This shows you the differences between two versions of the page.
en:tast_continuous_integration [2019/05/03 11:48] tast [Technical Continous Integration TAST-Jenkins] |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Technical Continous Integration TAST-Jenkins ====== | ||
- | |||
- | |||
- | |||
- | TAST integrates with Jenkins as a part of its Continuous Integration. | ||
- | |||
- | ===== Overview ===== | ||
- | |||
- | 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. | ||
- | |||
- | |||
- | ===== General Architecture View ===== | ||
- | |||
- | The following picture shows the general architecture view for enabling the solution of continuous integration between jenkins and TAST. | ||
- | |||
- | {{:undefined:tastcontinuousintegration.jpg?nolink|}} | ||
- | |||
- | |||
- | ===== Interchange Files ===== | ||
- | |||
- | This is the template that the input files should be created to launch the TAST-CI.jar with the proper content of test cases to be executed. | ||
- | |||
- | <?xml version="1.0"?> | ||
- | <jenkins> | ||
- | <sendRequest> | ||
- | <idTestSet>5507</idTestSet> | ||
- | <idLabHost>4</idLabHost> | ||
- | <user>pgarcia</user> | ||
- | <password>1234</password> | ||
- | </sendRequest> | ||
- | <sendRequest> | ||
- | <idTestSet>5518</idTestSet> | ||
- | <idLabHost>4</idLabHost> | ||
- | <user>pgarcia</user> | ||
- | <password>1234</password> | ||
- | </sendRequest> | ||
- | <sendRequest> | ||
- | <idTestSet>5528</idTestSet> | ||
- | <idLabHost>4</idLabHost> | ||
- | <user>pgarcia</user> | ||
- | <password>1234</password> | ||
- | </sendRequest> | ||
- | </jenkins> | ||
- | |||
- | |||
- | This is the template as the output files will be provided to Jenkins for registering the results (in JUnit Format): | ||
- | |||
- | <?xml version="1.0" encoding="UTF-8" standalone="no"?> | ||
- | <testsuites failures="1" tests="3" time="195000"> | ||
- | <testsuite errors="0" failures="1" name="02.01" skipped="0" tests="6" time="72000"> | ||
- | <testcase name="tcd_26.12" time="10000"/> | ||
- | <testcase name="tcd_26.12_7205" time="13000"/> | ||
- | <testcase name="tcd_26.12_7206" time="13000"/> | ||
- | <testcase name="tcd_26.12_7207" time="5000"/> | ||
- | <testcase name="tcd_26.12_7208" time="8000"/> | ||
- | <testcase name="tcd_TestingGates_2" time="23000"/> | ||
- | </testsuite> | ||
- | <testsuite errors="0" failures="0" name="04.01" skipped="0" tests="4" time="65000"> | ||
- | <testcase name="tcd_04.01" time="16000"/> | ||
- | <testcase name="tcd_04.01_7270" time="11000"/> | ||
- | <testcase name="tcd_04.01_7271" time="20000"/> | ||
- | <testcase name="tcd_04.01_7272" time="18000"/> | ||
- | </testsuite> | ||
- | <testsuite errors="0" failures="0" name="03.01" skipped="0" tests="4" time="47000"> | ||
- | <testcase name="tcd_03.01" time="14000"/> | ||
- | <testcase name="tcd_03.01_7258" time="6000"/> | ||
- | <testcase name="tcd_03.01_7259" time="15000"/> | ||
- | <testcase name="tcd_03.01_7260" time="12000"/> | ||
- | </testsuite> | ||
- | </testsuites> | ||
- | | ||
- | |||
- | |||
- | |||