You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem:
We have several different configurations on our project, for these configuration we have different suites of tests. This tests are managed by meta tags.
For each suite we have different table path. Some stories are runned only on 1 configurations and this stories have unique tables files.
Unfortunately, other suites are failing, because during project compilation, Vividus search this table for each suite, even when this story shouldn't be runned for this suite. But this table exists only for 1 configuration.
Error:
This happens, because in the project building flow, plan of executing tests(and checking table properties) are earlier that filtration by meta-tags
Current workaround:
We forced to create tables for each suites and they will never be used.
Possible solutions:
Make filtration earlier, before building plan for tests execution
The text was updated successfully, but these errors were encountered:
Problem:
We have several different configurations on our project, for these configuration we have different suites of tests. This tests are managed by meta tags.
For each suite we have different table path. Some stories are runned only on 1 configurations and this stories have unique tables files.
Unfortunately, other suites are failing, because during project compilation, Vividus search this table for each suite, even when this story shouldn't be runned for this suite. But this table exists only for 1 configuration.
Error:
This happens, because in the project building flow, plan of executing tests(and checking table properties) are earlier that filtration by meta-tags
Current workaround:
We forced to create tables for each suites and they will never be used.
Possible solutions:
Make filtration earlier, before building plan for tests execution
The text was updated successfully, but these errors were encountered: