TestNG ignores timeOut parameter if in XML specified parallel="tests"
See original GitHub issueHere is my test
public class TestTestNG {
@Test(timeOut = 500)
public void timeOutDoesNotWork() throws InterruptedException {
TimeUnit.HOURS.sleep(Long.MAX_VALUE);
}
}
and XML
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >
<suite name="TestNG test" parallel="tests">
<test name="Test TestNG" >
<classes>
<class name="ru.tpp.qadaemon.hermes.zigbee.TestTestNG" />
</classes>
</test>
</suite>
Test not fails by timeout Affect vesions starting with 6.1
Issue Analytics
- State:
- Created 9 years ago
- Comments:7
Top Results From Across the Web
Documentation - TestNG
This specifies the name for a test defined on the command line. This option is ignored if the suite.xml file or the source...
Read more >time out setting in TestNG doesn't work - Google Groups
in the xml suite file I defined, I have the "parallel" set to "tests", would this matter? I think TestNG spawns threads for...
Read more >Testng ignores @Test, when parameters are used
I am trying to execute a simple test wherein firefox browser and chrome browser open at once and they both fetch the same...
Read more >TestNG Parallel Execution - How to run Selenium tests in ...
As I mentioned, if we run the test methods directly through the test case file (Run As -> TestNG Test) rather than the...
Read more >Test methods, classes and groups - TestNG Docs
Specifying parameters in testng.xml might not be sufficient if you need to ... The @Ignore annotation has a higher priority than individual @Test...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@krmahadevan I upgrade to 6.14.3, it is works fine!!!
😃