Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
When I use 3.0.0-beta2 from 'mvn test' it seems to use TestNG instead of JUnit #2575
OS: Windows 10
Expected Behavior -
"mvn test" normally runs my tests using JUnit
Actual Behavior -
With beta2 "mvn test" seems to try and run with TestNG and as a result no tests are run
During the maven output I see:
If I change the version of Selenium to "3.0.0-beta1" my tests run normally.
If I change the version of Selenium 2 "2.53.1" my tests run normally.
This behaviour of 'no tests running' only happens when Selenium version is "3.0.0-beta2"
Steps to reproduce -
You could check out this project https://github.com/eviltester/wdci and change the version of webdriver to "3.0.0-beta2"
Have a look at the Travic-ci build that illustrates the problem:
This build is running against 2.53.1 and passes as normal
I amended the pom.xml to use 3.0.0-beta1
This ran the test as expected, and failed as expected because wires.exe is not available and 3.0.0 defaults to Marionette for Firefox.
I then amended the pom.xml to use 3.0.0-beta2 expecting the same results as the beta1 build, but no tests ran and the build tries to use TestNG
Then I change it back to 2.53.1 to get the build back to normal
looks like our dependency tree shifted quite a bit with simon and my tinkering :)
I will be checking it out further, but in beta1 testng is a dependency of the leg-rc package and you likely didn't include it explicitly and selenium-server did not depend upon it. In beta2 it seems to have leg-rc as a dependency of selenium-server. Going to check on our assumptions again on this, if that's the right thing to do or not.
ok.. so the pom's (and thus the maven dependency:tree) are going to change, but because of the leg-rc package that includes some TestNG extensions, testng is going to be included as a dependency. selenium-server -> leg-rc -> testng
If you don't require Selenium RC or WebDriverBacked selenium I would recommend excluding the leg-rc pacakge:
Or if you do need them, you can just exclude testng.
Sadly this is going to be around until ~4.0
The pom's in beta2 are still messed up a bit, but the changes won't affect this issue (i think)
Worked for me.
it won't be in beta3... since leg-rc will need to be explicitly included (which is what pulled in the transitive dependency of testng).
So, this is "fixed", when we release I'll update the maven downloads page on seleniumhq to talk about including the leg-rc package