{"id":19279,"date":"2017-03-15T13:11:20","date_gmt":"2017-03-15T13:11:20","guid":{"rendered":"https:\/\/www.testingdocs.com\/questions\/?p=19279"},"modified":"2024-12-09T17:17:08","modified_gmt":"2024-12-09T17:17:08","slug":"what-is-invocationtimeout-in-testng","status":"publish","type":"post","link":"https:\/\/www.testingdocs.com\/questions\/what-is-invocationtimeout-in-testng\/","title":{"rendered":"What is invocationTimeOut in TestNG?"},"content":{"rendered":"

What is invocationTimeOut in TestNG?<\/h2>\n

In this tutorial, let’s understand invocationTimeOut<\/strong> test method attribute in TestNG. In TestNG, we can specify the number of times the method can be invoked using the invocationCount<\/strong> attribute. This attribute is the number of times the test method would be invoked during the run.<\/p>\n

invocationTimeOut<\/h3>\n

When we set invocationCount<\/strong> and invocationTimeOut<\/strong> on a test method, invocationTimeOut<\/strong> is the maximum time period TestNG will wait for all the invocations of the test method specified in the attribute invocationCount<\/strong>.<\/p>\n

This attribute specified is in milliseconds of time. For example, to specify 6 secs we have to use<\/p>\n

invocationTimeOut=6000<\/p>\n

Let’s see a simple example. The test method executes 5 times.( invocationCount=5)<\/p>\n

 <\/p>\n

\"invocationCount<\/p>\n

 <\/p>\n

Sample Code Listing<\/h3>\n
package com.testingdocs.testng.tutorials;\r\n\r\nimport org.testng.annotations.Test;\r\n\/\/www.TestingDocs.com - TestNG Tutorials \r\npublic class TestNGInvocationCount {\r\n \r\n\t@Test(invocationCount=5,invocationTimeOut=6000)\r\n\tpublic void sampleTest() throws Exception{\r\n\t\tSystem.out.println(\"Foo.\");\r\n \t\tThread.sleep(1000);\r\n\t}\r\n}\r\n<\/pre>\n
 <\/p>\n
Output<\/h3>\n
Foo.
\nFoo.
\nFoo.
\nFoo.
\nFoo.
\nPASSED: sampleTest<\/p>\n
===============================================
\nDefault test
\nTests run: 1, Failures: 0, Skips: 0
\n===============================================<\/p>\n
The invocationTimeOut specified in the Test is 6000 ms. The test passed because all the test method invocations executed before the invocationTimeOut<\/strong>.<\/p>\n
The method waits for 1000 ms.<\/p>\n
invocationTimeOut<\/strong> > ~ 5 * 1000 ms<\/p>\n
Since 6000 > 5*1000 +(small delta ) <\/strong>the test is marked as pass.<\/p>\n
timeOut vs invocationTimeOut<\/h3>\n
Test annotation has another attribute called timeOut<\/strong>. This attribute is the maximum time the method should take to complete. If we mix both the attributes the timeOut will override the invocationTimeOut<\/strong> value.<\/p>\n
 <\/p>\n
package com.testingdocs.testng.tutorials;\r\n\r\nimport org.testng.annotations.Test;\r\n\r\n\/\/www.TestingDocs.com - TestNG Tutorials \r\n\r\npublic class TestNGInvocationCount {\r\n \r\n\t@Test(invocationCount=5,invocationTimeOut=6000,timeOut=900)\r\n\tpublic void sampleTest() throws Exception{\r\n\t\tSystem.out.println(\"Foo.\");\r\n \t\tThread.sleep(1000);\r\n\t}\r\n}\r\n<\/pre>\n
 <\/p>\n
\"invocationTimeOut<\/p>\n
 <\/p>\n
The test would be marked as failure as the timeOut<\/strong> attribute overrides the invocationTimeOut<\/strong> value. i.e When both the values are specified the test run time should be less both the values for the test to be marked as pass.<\/p>\n
Test runs that exceed the timeout will fail with the ThreadTimeoutException:<\/strong><\/p>\n
org.testng.internal.thread.ThreadTimeoutException: Method \r\ncom.testingdocs.testng.tutorials.TestNGInvocationCount.sampleTest() \r\ndidn't finish within the time-out 900<\/pre>\n
 <\/p>\n
TestNG Tutorials on this website can be found at:<\/p>\n