NicolasPelletier / js-test-driver

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

Changed files not getting loaded once server has been started #306

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. start a server session
2. run tests and verify pass
3. make a change to the target method which the test cases have been written 
for to purposely fail.
4. rerun test

What is the expected output? What do you see instead?
The test should fail
Result: test still passes because updates to this file are not loaded

What version of the product are you using? On what operating system?
1.3.3d

Please provide any additional information below.
I see this only on the files/methods for which the tests are written for. This 
is preventing me from writing my test cases to fail first then writing the 
proper code to make them pass.

Original issue reported on code.google.com by troyw...@gmail.com on 7 Dec 2011 at 9:54

GoogleCodeExporter commented 9 years ago
Please recreate the issue with --runnerMode=DEBUG, and attach the appropriate 
log file from <tmp directory/jstd-<timestamp>.log

Original comment by corbinrs...@gmail.com on 7 Dec 2011 at 3:04

GoogleCodeExporter commented 9 years ago
I've attached the log and a small test project that I'm using to verify this 
issue.

I first run the against this block of code to get the test to pass.

if(!String.prototype.trim) {
    String.prototype.trim = String.prototype.replace.curry(/^\s+|\s+$/, '');
}

then change this method to return null expecting the test to fail.

if(!String.prototype.trim) {
    String.prototype.trim = null;
}

Original comment by troyw...@gmail.com on 7 Dec 2011 at 4:30

Attachments:

GoogleCodeExporter commented 9 years ago
Hmmm. According to the log, the cache is being updated.

What is the sequence command being run?

Original comment by corbinrs...@gmail.com on 7 Dec 2011 at 8:45

GoogleCodeExporter commented 9 years ago
Is this what you need? If not let me know, thanks.

jstd --port 42242
jstd --tests all

Original comment by troyw...@gmail.com on 7 Dec 2011 at 9:32