TestNG run order breaking dependent tests

[justingraham12]

Due to TestNG running dependent tests out of order the current TestNG-Webdriver implementation is overwriting the webdriver field with a new webdriver instance. Need to evaluate how we update the Webdriver field.

[justingraham12]

I have not been able to find a resolution to this problem. TestNG doesn't have a way to specify that dependent methods must run together. And when we kick off a test in another class the initial webdriver instances becomes orphaned. I believe this is due to the webdriver reusing the port of the previous driver...

[nimret]

dunno if this helps:
http://stackoverflow.com/questions/2669576/order-of-execution-of-tests-in-testng

shouldn't the tests be modular and not dependent? or is that because it takes too long otherwise to setup and run the tests?

just curious :)

[justingraham12]

Unit tests should be kept modular as much as possible. However anything higher level than that (functional, integration, UI) usually requires many "steps" to execute. By dividing the steps into individual tests that depend on each other it keeps each step condense and focused. Also a failing test tells you exactly where you have a problem and TestNG will skip all dependent steps thus saving you time.

The issue I'm referring to with this bug is the fact that TestNG, while executing dependent tests within a single class, will sometimes slip in unit tests from another class in between the dependent ones.

The ClassDriver was built to allow a WebDriver to run across dependent tests. But due to the injected 3rd test from another class we lose our reference to the ClassDriver. For an example of this take a look at the bug_1 test directory within testng-webdriver hot fix branch.

[nimret]

I'd have to pair to understand the problem better. Sounds like a reference is losing the instance it points to at runtime due to injection from another class. Doesn't sound like a good thing or fun.