search

carlorizzante / js-test-driver

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

Cached files between test runs #421

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Run tests for awhile in either Chrome or Firefox
2. At some point change a file in a way that would fix a test
3. Run tests again
4. See your test fail ... on a line that no longer exists because you deleted 
it when you fixed the test
5. Hard refresh the browser (not sure if the "hard" part is necessary)
6. See your test pass as expected

What is the expected output? What do you see instead?
I expect to see changes I make in files reflected in test output (not tests run 
against stale cached files).

What version of the product are you using? On what operating system?
1.3.4.b  (I tried to use 1.3.5 but it broke everything so I'm waiting for 
1.3.5.a).  Nothing in the release notes for 1.3.5 (that I could see at least) 
suggested that it would fix this issue, but I may just have mis-read the list.

Please provide any additional information below.
I wish I could provide a sample test case that causes the problem every time, 
but it's intermittent.  Furthermore, the test content itself doesn't *seem* to 
be relevant; any of my tests seem to (potentially) cause this issue.

The one sort of unique thing about my environment is that I don't load 
everything in jstestdriver.conf.  Instead, I load some stuff, serve the rest, 
and then use Require.js to load the served files.  So this caching thing could 
very well be served-content-specific.

Original issue reported on code.google.com by jer...@syapse.com on 31 Jan 2013 at 6:31

GoogleCodeExporter commented 8 years ago 
P.S. I should have mentioned that whenever I've seen this issue, the cached 
files have always been Require-loaded/served files.  That doesn't necessarily 
mean anything though, because I almost never edit my non-served files (they're 
all stuff like jQuery).

Original comment by jer...@syapse.com on 31 Jan 2013 at 6:33

GoogleCodeExporter commented 8 years ago 
P.P.S In chrome this happens even when I have the developer tools up with the 
no cache option on; this further suggests to me that the caching is happening 
server-side.

Original comment by jer...@syapse.com on 31 Jan 2013 at 6:33