We have a test suite which has recently grown to just over 200 tests. Recently I have started experiencing an issue on our build server whereby the test run appears to hang at around 150 tests and subsequently bombs out with a ChutzpahTimeoutException. Interestingly the number of tests after which it hangs varies between runs, but is always around 150.
We can run the tests locally fine, but our development machines are quite powerful compared to the build server.
I am using Chutzpah 2.2.1.173 and our tests are written in Jasmine using RequireJS.
Comments: You make a good point. If you are loading are files with AMD then Chutzpah looks at is as one big test run and the timeout will kill it all. It would be nice to run them individually but to do so would require parsing require() paths. I haven;t thought much about this and am not sure how well it would work.
We can run the tests locally fine, but our development machines are quite powerful compared to the build server.
I am using Chutzpah 2.2.1.173 and our tests are written in Jasmine using RequireJS.
Comments: You make a good point. If you are loading are files with AMD then Chutzpah looks at is as one big test run and the timeout will kill it all. It would be nice to run them individually but to do so would require parsing require() paths. I haven;t thought much about this and am not sure how well it would work.