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
I think it's time to deprecate smart steps and foresee their removal: I still see it used from time to time in company we train/coach. It leads to slow suites, thus slowing down feedback cycle; and totally violates FIRST principles.
However what's possible with smart steps is also possible without.
We can create steps that call other steps, from the same context or even from another context.
IMHO, there's no real use case of such a feature. Hence I would be glad to see it removed from this package, so we don't have anymore to explain why, in one hand, it's so bad that it should not be used, and in the other hand why we keep it. What do you think?
Hello everyone,
I think it's time to deprecate smart steps and foresee their removal: I still see it used from time to time in company we train/coach. It leads to slow suites, thus slowing down feedback cycle; and totally violates FIRST principles.
However what's possible with smart steps is also possible without.
IMHO, there's no real use case of such a feature. Hence I would be glad to see it removed from this package, so we don't have anymore to explain why, in one hand, it's so bad that it should not be used, and in the other hand why we keep it. What do you think?