LiTiang / js-test-driver

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

Excessive logging causes test runs not to be reported correctly if captureConsole is enabled #182

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
1. Start a server and run the attached test case with --captureConsole

Expected output is one test error, and a significant amount of logging.
Actual output indicates that no tests were run.

2. Without restarting the server or reloading the browser, run the test case 
again

Expected output is the same as last time.
Actual output is one test error and a significant amout of logging, but the 
timestamps in the log output indicate that this is the result of the previous 
test run.

This was tried with jsTestDriver 1.2.2 on Linux.

Tested browsers were:
- Chromium 8.0.552.224 (68599) Ubuntu 10.10
- Firefox 3.6.13 on Ubuntu
- Chrome 8.0.552.231 on Mac OS X
- Firefox 3.5.5 on Mac OS X

When the results of the first test run are reported the browser is still 
displaying: "Running: command= 
{"command":"runAllTests","parameters":["true","false",""]}"

It seems that the test is not reported as run until it is run at least twice, 
and the result of the second to last run is reported.

Original issue reported on code.google.com by nicklas....@gmail.com on 27 Dec 2010 at 10:49

Attachments: