search

fhigit / js-test-driver

Automatically exported from code.google.com/p/js-test-driver
0 stars 0 forks source link

Ability to change callback timeout for async test cases #243

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
The page at http://code.google.com/p/js-test-driver/wiki/AsyncTestCase explains 
that "The test runner will not execute any subsequent step in the queue until 
all outstanding callbacks of the current step are complete. If the callbacks 
are not a called for an egregious amount of time, currently set to 30 seconds, 
the test fails."

I'm using js-test-driver for stress-testing of our JavaScript library that 
performs calls to web services using AsyncTestCase. 

Unfortunately I am hitting the 30second limit for callbacks when I attempt to 
perform thousands of web services calls and am forced to lower the number of 
calls the test performs just to stay within this 30second limit.

Being able to change this 30second limit through command line arguments / 
config file would allow me to perform heavy stress testing without calling the 
same small stress-test over and over again.

Original issue reported on code.google.com by Greg.Bag...@gmail.com on 16 May 2011 at 11:56

GoogleCodeExporter commented 9 years ago 
In day to day testing, the 30 seconds are a real pain. It would save a lot of 
time (and nerves :)) if this could be configured via some kind of argument or 
setting since in most cases a timeout of a few seconds will do.

Original comment by peter.ri...@gmx.net on 9 Feb 2012 at 7:39