3.5.3 Execution Flows - AND Operator

Abbreviations, used in manual:

EF - Execution Flow

Starting from quilliup version 2.6.1.6, the AND operator (switcher "Disable AND") is available in EFs and is enabled by default. This operator is relevant when an element has multiple incoming connections, as illustrated in the example below with the 'Test 4' element:

The "Disable AND" switcher has two states:

•  

  • Enabled (default):

    In this mode, the execution of a test depends on the status of all its preceding connections. The AND operator plays a key role in this behavior within Execution Flows (EFs).

    When an EF element has multiple entry points or connections - like in the example of 'Test 4' -the "Disable AND" switch ensures that this element will only execute if all the previous connections meet their specified conditions.

    To clarify, consider the conditions for 'Test 4':

    • Test 1: must complete with both "Failure" (burgundy) and "Complete" (grey) statuses.

    • Test 2: must complete with a "Success" status (green).

    • Test 3: must complete with a "Failure" status (burgundy).

    "Test 4" will only be triggered and executed when all these conditions are satisfied. If any of the preceding tests or elements fail to meet their specific requirements, "Test 4" will not run. This ensures controlled test execution aligned with the defined EF logic.

    This feature offers a robust way to manage test execution based on dependencies, enabling more structured and efficient testing workflows.

• Disabled:

In this scenario, each path or connection will run independently, just like a regular Execution Flow (EF). There is no interdependence between the paths, allowing tests to run more than once based on their individual conditions.

For instance:
1. If "Test 2" element completes with the "Failure" (as "Test 1" element's condition is "Complete"), "Test 4" element will be implemented.
2. If "Test 1" element completes with the status "Warning" and "Test 3" element completes with the status  "Success", "Test 4" element will be implemented.

In this setup, the paths operate autonomously, providing flexibility and allowing Tests/elements to be executed based on their respective conditions without any constraints imposed by other paths or connections. This ensures that the Test execution process aligns precisely with the defined conditions for each individual path.