Many tests are not run

[otakustay]

Below I would describe a interesting behavior saga shows, the reproduce steps are:

1. git clone git://github.com/ecomfe/esui.git
2. cd esui/test
3. java -jar <saga-cli.jar> -b . -o ./target [-v CHROME/FIREFOX_17/INTERNET_EXPLORER_9]
4. View the report

I got 3 different result set with 3 different browser, in FIREFOX_17 whcih is the default value of -v arg, it gives an about 80% coverage, but with CHROME I got just 15%.

I don't think such low coverage is normal, so I inpected the result and found when using CHROME as the browser, almost nothing runs.

Since we use a custom AMD loader to load test asynchronously, I suppose that saga collects coverage result when page's onload event fires, but our jasmine tests run after onload so is ignored by saga, but this did not explain why FIREFOX_17 got high coverage result.

[timurstrekalov]

If you are using AMD, that would be the problem, since there's still a ticket (#42) open for AMD support. AMD experts are welcome to grab it.