test.guide 2025 Q1

Dynamic Playbook filter steps

Managing packages and projects in Playbooks is much easier and faster with the new dynamic Playbook filter steps.

Instead of statically defining which individual packages and projects in a workspace should be used for a playbook, you can now store filter rules for attributes, test script IDs or test suite IDs. The filters are evaluated live during playbook execution. The resulting test execution tasks contain only the package or project steps that explicitly match the filter.

Note: As a prerequisite for this feature, the workspace sources and dependencies must be integrated as a Git repository.

test.guide Release 1.184.0.0 Dynamische Playbook-Filterschritte

test.guide Release 1.184.0.0 Dynamische Playbook-Filterschritte

Benefits of filtering

  • Simplified playbook definition
    By using dynamic filter steps, you can significantly simplify both definition and manual maintenance.

  • Dynamic update
    Changes in the Git repository are reflected live each time a playbook is run. New or changed packages and projects automatically appear in the next execution task.
  • Consistent and repeatable test execution
    Each execution task contains explicit steps that reflect exactly the state at the time of filtering. This enables reproducibility at any time, regardless of subsequent changes to the workspace.