Technical Continous Integration H-TEST-Jenkins

https://wiki.htest.testautomationsystemtool.com/books/h-test/page/infrastructureH-TEST integrates with Jenkins as a part of its Continuous Integration.

Overview

The objective is to manage the integration between Jenkins and H-TEST in order to allow the execution of the regression test after each deployment done inside the Pipeline. For enabling the integration between Jenkins and H-TEST, two main components are going to be provided by H-TEST:

• H-TEST-CI MicroService API: Allocated in the H-TEST server will make possible to publish the methods for executing and providing results to Jenkins.
• H-TEST-CI.jar: Executable to be run for calling the H-TEST execution.

General Architecture View

The following picture shows the general architecture view for enabling the solution of continuous integration between Jenkins and H-TEST.

API Call

The H-TEST-CI MicroService API allows to order the execution of an Application in order to run the regression tests after a deployment. An Application is a group of Test Sets that have been packed for a specific Environment. The API call is built as follows:

• Call Type: GET
• EndPoint: https://app.cloud1.testautomationsystemtool.com/clientJenkins/executeRemoteCITest
• Parameters:
  • application: name of the Application as defined in H-TEST.
  • environment: environment linked to the Application as defined in H-TEST.
  • urlPositive: url for Positive result.
  • urlNegative: url for Negative result.

Example:

• application: test_application
• environment: CERT_environment
• urlPositive: http://localhost:8080/tast/client/getGreeting
• urlNegative: http://localhost:8080/tast/client/getGreetingKO
• Final call: https://app.cloud1.testautomationsystemtool.com/clientJenkins/executeRemoteCITest?application=test_application&environment=CERT_enviroment&urlPositive=http://localhost:8080/tast/client/getGreeting&urlNegative=http://localhost:8080/tast/client/getGreetingKO

Please note that urlPositive and urlNegative are not fixed url's, they will be provided by the responsible of the deployment.

application/environment can exist only once in the DDBB.

The mentioned Endpoint belongs to TAST2 installation; to obtain the endpoint of other environments please refer to your local support.

Pipeline Integration / Defining the Infrastructure

Para implementar la prueba de regresión en la integración continua, Infraestructura permite definir Pools que contienen las Aplicaciones que deben ser probadas; estas aplicaciones se definen mediante la agregación de los TestSets que deben ser ejecutados. También puede decidir allí el Host Lab que se utilizará para la ejecución.

Puedes tener una explicación completa de cómo usarlo aquí.