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
In the example there's two different 'dependency hierarchy branches'. I was expecting to receive an empty stack in testSomethingElseThatWantsAnEmptyStack, but instead it seems that the earlier branch affected the state of the stack. Is this intended behavior? Am i doing something wrong? Is this a known limitation that is unfortunately a necessary evil for performance reasons? (I think the dependency would need to be rerun for every branch?)
There are workarounds of course, but they don't seem as elegant as having multiple tests that depend on the same 'parent' test.
The text was updated successfully, but these errors were encountered:
I may be doing something wrong or maybe I'm missing something. This is a very simplified version of the type of class I'm trying to test:
And the test:
In the example there's two different 'dependency hierarchy branches'. I was expecting to receive an empty stack in
testSomethingElseThatWantsAnEmptyStack
, but instead it seems that the earlier branch affected the state of the stack. Is this intended behavior? Am i doing something wrong? Is this a known limitation that is unfortunately a necessary evil for performance reasons? (I think the dependency would need to be rerun for every branch?)There are workarounds of course, but they don't seem as elegant as having multiple tests that depend on the same 'parent' test.
The text was updated successfully, but these errors were encountered: