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

[NonInterruptiveEvent]: being able to have a default value for the parameter PHASED.TESTS.PHASE #214

Open
mickaelgobbo opened this issue Oct 7, 2024 · 2 comments

Comments

@mickaelgobbo
Copy link

Expected Behaviour

Currently we have different way to execute different combination of testing with even, but the -DPHASED.TESTS.PHASE parameter is mandatory to being able to execute non interrutive event.

For exemple we can have for now the mode 23 (-DPHASED.TESTS.PHASE='NON_INTERRUPTIVE(23)') to be sure that
the event is finished before calling the test method.

We have also the mode 33 (-DPHASED.TESTS.PHASE='NON_INTERRUPTIVE(33)') to call in the same time the event and the test
method to allow a completely different scenarion.

Improvement request

We need probably to have a default mode, to being able to trigger test method with even without this parameter.

I think the NON_INTERRUPTIVE(23) should be a good candidate for a default mode, given it's in this mode we have better chance
to reproduce the same exactly STR in case of reexecution of test.

@mickaelgobbo
Copy link
Author

there is indeed a dafault mode which is 33 if we specify the parameter -DPHASED.TESTS.PHASE='NON_INTERRUPTIVE'
it's fine so.

@baubakg
Copy link
Member

baubakg commented Oct 8, 2024

This is part of the refactoring #204
I will add this as an item for that issue

@baubakg baubakg reopened this Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants