TAST integrates with Jenkins as a part of its Continuous Integration.

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

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

The following picture shows the general architecture view for enabling the solution of continuous integration between jenkins and TAST.

The TAST-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://tast-sbg-tast-pre.appls.boaw.paas.gsnetcloud.corp/clientJenkins/executeRemoteCITest
• Parameters:
  • application: name of the Application as defined in TAST
  • environment: Environment linked to the Application as defined in TAST
  • 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://tast-sbg-tast-pre.appls.boaw.paas.gsnetcloud.corp/clientJenkins/executeRemoteCITest?application=test_application&environment=CERT_enviroment&urlPositive=http://localhost:8080/tast/client/getGreeting&urlNegative=http://localhost:8080/tast/client/getGreetingKO

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