New mechanism to skip tasks and suites#271
Open
sergiocazzolato wants to merge 1 commit intocanonical:masterfrom
Open
New mechanism to skip tasks and suites#271sergiocazzolato wants to merge 1 commit intocanonical:masterfrom
sergiocazzolato wants to merge 1 commit intocanonical:masterfrom
Conversation
A skip condition determines whether a task or suite should be skipped before it begins execution. Skip conditions can only be defined at the task or suite level. They are evaluated before the task preparation phase. If the condition evaluates to true, the entire task or suite is skipped — including the prepare, execute, and restore phases. We considered introducing a SKIP command similar to REBOOT, but this approach implies partially running the prepare phases (e.g., prepare-each at project/backend/suite level). This means the task wouldn’t actually be skipped, and determining what should be restored becomes unclear. Using a skip condition is cleaner and more predictable from a developer’s perspective, and aligns with how skip/conditional execution works in most testing tools across languages.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A skip condition determines whether a task or suite should be skipped before it begins execution.
Skip conditions can only be defined at the task or suite level. They are evaluated before the task preparation phase. If the condition evaluates to true, the entire task or suite is skipped — including the prepare, execute, and restore phases.
We considered introducing a SKIP command similar to REBOOT, but this approach implies partially running the prepare phases (e.g., prepare-each at project/backend/suite level). This means the task wouldn’t actually be skipped, and determining what should be restored becomes unclear.
Using a skip condition is cleaner and more predictable from a developer’s perspective, and aligns with how skip/conditional execution works in most testing tools across languages.
Executed locally the tests: https://pastebin.canonical.com/p/P7fxgCPdb3/