Well, I am not sure if anyone else will have this problem but I have kind of a fix for it. Qunit detects url params for tests. If the param is not a valid test it returns. Testswarm puts a bunch of params in the url for the tests so it bugs it out. If you comment out line 82-84 which tests for valid tests it will run. Maybe I didn't something up right. But I figure if someone else runs in to this they can check it out.
On Oct 7, 4:31 pm, Ryan S <[email protected]> wrote: > So after muddling my way through I have hit a roadblock. I can submit > jobs and connect clients. When a client connects the job starts to run > but it looks like there are no tests being run in the iframe. The > inject script is there and if I go to the test page that was created > after I run the submit script it runs fine. So I look at the results > and all I see is > this:http://cocodev.com/screenshots/ryan/6876add93cfdf32f5508430512627fb0.png > > OK after looking at the access logs there are parameters that > apparenlty break the test/index.html. > > ::1 - - [07/Oct/2009:16:28:17 -0500] "GET /~ryan/changeset/c052611/ > test/?_=1254950897776&swarmURL=http%3A%2F%2Ftestswarm.local%3Frun_id > %3D16%26client_id%3D25%26state%3D HTTP/1.1" 200 747 > > Anyone have any idea why the url params would stop the test from > running? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TestSwarm" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/testswarm?hl=en -~----------~----~----~----~------~----~------~--~---
