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
Now if both ClassA and ClassB have been chosen for execution, then TestNG is currently doing the following:
ba() is first executed before running aa(). This assures that TestNG is honouring cross class method dependencies.
But if ba() fails, then TestNG should be skipping ClassA.aa() (because of the dependency) but it does not do that and instead runs aa() despite there being a failure in upstream.
The same behaviour is seen even when we use dependsOnMethods to refer to a method in a inner nested class.
Test case sample
Please, share the test case (as small as possible) which shows the issue
TestNG Version
Expected behavior
dependsOnMethods
attribute should honour upstream failures when it spans across instances rather than the same instance.Actual behavior
Upstream failures are confined to ONLY the current instance but does not span across instances.
Is the issue reproducible on runner?
Issue summary
Let's say we have two test classes.
ClassA
ClassB
Lets assume that
aa()
has been defined as below:Now if both ClassA and ClassB have been chosen for execution, then TestNG is currently doing the following:
ba()
is first executed before runningaa()
. This assures that TestNG is honouring cross class method dependencies.But if
ba()
fails, then TestNG should be skippingClassA.aa()
(because of the dependency) but it does not do that and instead runsaa()
despite there being a failure in upstream.The same behaviour is seen even when we use
dependsOnMethods
to refer to a method in a inner nested class.Test case sample
ClassATestClassSample
ClassBTestClassSample
NestedTestClassSample
TestResultsGatherer
Test case
The text was updated successfully, but these errors were encountered: