Open schroeca opened 2 years ago
@schroeca - Do you know if this ever worked? I have been searching through the codebase to find any evidence of this working and so far its been a dead end. Couldn't even find a single test also that vets this out. So if you know in which version it worked, it would be good if you could please share that information so that I can dig in from there.
I got feedback from my team colleague that it was working in 7.0.4.
I have tested this by myself with various different versions for the past 3 weeks and it was never working.
I guess the test case my colleague used for testing was simply wrong.
Would it be possible to add the described "expected" behavior in one of your next releases?
@schroeca - Thanks for the quick turnaround. This issue is going to be a bit more complicated to fix, so please bear with the delay.
I will first try and cross compare the behaviour for @Test
method. The behaviour for this also should be on par with how @Test
with groups
and dependsOnGroups
behaves in terms of group selection, and it would also have all the behaviour of a configuration annotation
TestNG 7.1.0
Expected behavior
The method annotated with @beforeGroups and all tests included in the defined group shall not be executed until all tests of the group on which the current group depends have finished. This includes also the @beforeGroups and @afterGroups method associated with the defined "depends on" group.
Actual behavior
The beforeGroups method and the tests included in group A are called after the beforeGroups method and the tests of group B. But group A is defined as "dependsOnGroup B".
Is the issue reproducible on runner?
Test case sample
Intellij output