Describe the bug
Priorities were broken after upgrading to version 9, tests are run in random order, ignoring the priority parameter
To Reproduce
Steps to reproduce the behavior:
-
Run tests with parameter priority, example:
"@test(testName = "Check popup for withdraw funds", priority = 1)
@test(testName = "Check....", priority = 2)"
-
Run on 2.13.8 and run on 2.13.9
Expected behavior
On 2.13.8 we have first priority 1, then the priority 2
On 2.13.9 we have first priority 2, then the priority 1 or another random priorities
Selenide Version: 5.20.1
Chrome\Firefox\IE Version: 89 Chrome
Browser Driver Version: 4.3.1
Selenium Version: 3.141.59
Describe the bug
Priorities were broken after upgrading to version 9, tests are run in random order, ignoring the priority parameter
To Reproduce
Steps to reproduce the behavior:
Run tests with parameter priority, example:
"@test(testName = "Check popup for withdraw funds", priority = 1)
@test(testName = "Check....", priority = 2)"
Run on 2.13.8 and run on 2.13.9
Expected behavior
On 2.13.8 we have first priority 1, then the priority 2
On 2.13.9 we have first priority 2, then the priority 1 or another random priorities
Selenide Version: 5.20.1
Chrome\Firefox\IE Version: 89 Chrome
Browser Driver Version: 4.3.1
Selenium Version: 3.141.59