Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate execution mode from phases. #204

Open
baubakg opened this issue Sep 23, 2024 · 0 comments
Open

Separate execution mode from phases. #204

baubakg opened this issue Sep 23, 2024 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@baubakg
Copy link
Member

baubakg commented Sep 23, 2024

We need to create a property called execution mode that includes:

  • Interruptive(PRODUCER, CONSUMER)
  • Non-interruptive(23,33, ALL, STD)
  • permutational
  • Non-Phased (DEFAULT)

Phases will be types for each of these execution modes:

  • Producer
  • Consumer
  • NIE_23
  • NIE_33

Cleanup tasks:

  • Remoce Non-interruptive from Phases
  • Deprecate PHASES

We will be backward compatible for the next two versions. Where PHASES and ASYNCHRONOUS will still work, but will be deprecated.

Rules:

  • backward compatible with Phased tests interruptive (the very least)
  • If
  • (optional) Non-Interruptive -> Asynchronous. When executing Asynchronous we will actually run NIE_33
  • If MUTATIONAL.EXECUTION.MODE is set it takes precendence over PHASED.TESTS.PHASE.
  • PHASED.TESTS.PHASE taken only into account if MUTATIONAL.EXECUTION.MODE not set.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant