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
Currently all step definers, as in subclasses of StepDefiner, are loaded by default before test case starts, which may require to make sure that steps expressions are not ambiguous and results in issues like #17
Probably the simplest solution to that would be to allow each test to specify what step definers it uses to load only their steps.
This behaviour is also inconsistent in native and core tests, which is fixed with #131
Currently all step definers, as in subclasses of
StepDefiner
, are loaded by default before test case starts, which may require to make sure that steps expressions are not ambiguous and results in issues like #17Probably the simplest solution to that would be to allow each test to specify what step definers it uses to load only their steps.
This behaviour is also inconsistent in native and core tests, which is fixed with #131
Thoughts @kerrmarin @deanWombourne ?
The text was updated successfully, but these errors were encountered: