04.01 - Squash-TA Workflow


Squash-TA workflow

At first, there is an initialization of contents of the following directories: Targets, repositories and shortcuts. At this step, the different elements of those directories are verified and if everything is ok they are available for all the execution duration therefore for all different ecosystems to execute.

Afterwards there is the execution of the different ecosystems. Each of them with its own ecosystem context and for each test case its own test context. Whatever status an ecosystem has after its execution, the next ecosystem of the test suite is launched. 

Once all ecosystems have been executed, there is a cleaning-up step and finally the publication of the execution report available in the 'target' directory.

Here is a scheme of the Squash-TA workflow:


Squash-TA Test flow

Here is the Squash-TA Test flow since the v1.6.0 of Squash-TA framework (for previous flow see this page)  

   Exception raised by an instruction other than an assertion using the VERIFY mode(*)  Exception raised by an assertion instruction using the VERIFY mode(*)
 Ecosystem setup phase 
(setup.ta)
  • Stop the execution of this setup.ta Script and launch the teardown.ta script.
  • Execute the next instruction in the setup.ta script.
  • When the setup.ta script is finished, the test case of the ecosystem are launched.
 Test case SETUP phase
  • Stop the execution of this test case setup phase and launch the test case teardown phase.
  • When the test case teardown phase is finished, the next TA script (test case or teardown.ta) is launched
  • Execute the next instruction in this test case setup phase.
  • When this test case setup phase is finished, the test case test phase is launched.
 Test case TEST phase
  • Stop the execution of this test case test phase and launch the test case teardown phase.
  • When the test case teardown phase is finished, the next TA script (test case or teardown.ta) is launched
  • Execute the next instruction in this test case test phase.
  • When this test case test phase is finished, the test case teardown phase is launched.
 Test case TEARDOWN phase
  • Stop the execution of this test case teardown phase and launch the next TA Script (test case or teardown.ta).
  • Execute the next instruction in this test case teardown phase.
  • When this test case teardown phase is finished, the next TA Script (test case or teardown.ta) is launched.
 Ecosystem teardown phase 
(teardown.ta)
  • Stop the execution of this teardown.ta Script and launch the next ecosystem.
  • Execute the next instruction in this teardown.ta Script.
  • When this teardown.ta Script is finished the next ecosystem is launched.

(*) Exception could be an assertion failure or an unexpected error.


Squash-TA Status

Here is the Squash-TA status since the v1.6.0 of Squash-TA framework (for previous status see this page)  

 Element Status 
Instruction
  • If an instruction was not executed, its status is: "NOT RUN"
  • If an instruction was successfully executed, its status is: "SUCCESS"
  • If an assertion failure is raised, the instruction status is: "FAILURE
  • If an instruction raised an unexpected error, its status is: "ERROR"
Test case Phase
  • If a phase of a test case was not executed then its status is: "NOT_RUN"
  • Else its status is the most severe status among the status of its instructions
Script TA (Test)
  • If the script was not executed then its status is: "NOT_RUN"
  • Else its status is the most severe status among the status of its instructions
Ecosystem
  •  The most severe status among the status of its scripts


Comments