Test timed out again and again.. about testswarm

[Krinkle]

Which test framework are you using?

If you implemented a custom one, please consider submitting a PR so that I can review it for you and point out where it went wrong.

It sounds like you forgot to bind the proper handlers for either the ping, complete or submit events. As a result, even when the test is actually done, the inject script isn't being notified and as such keeps doing nothing until eventually the server discards the client when it still hasn't submitted any results. At this point the job is put back in the pool of pending tests for another client to run.

I'm using funcunit framework, I didn't wrote it yet in the inject.js because I didn't use it so far.. (I know its weird)

I'm using the steal.js to make my test from the framework funcunit. I thought that it would works at least a bit because its like the Qunit test no ?

I'm sorry if I ask too much, but I really don't know how to implement this new framework into testswarm.. :/

[JamesMGreene]

It's like QUnit except that it has a dependency on Selenium. Does your TestSwarm setup now how to handle that?

[Krinkle]

I haven't used FuncUnit specifically much, but in general, until you show some code, I can only recommend:

• Move it to inject.js; Look at inject.js#section-qunit for how to write the small bridge you need to add. Add a similar one for FuncUnit.
• Verify that you are loading TestSwarm's inject.js from your own TestSwarm server (not github, not swarm.jquery.org) in your test suite (jQuery example, MediaWiki example)

[jeff-harnois]

I ran into a similar issue; mine turned out to be the order of the scripts. inject.js needs to be included last, so that it can register some hooks into the test, so if you are not careful with your script order (mine was because I had it in the wrong place using require) then the hook doesn't attach properly and won't ever fire back.