Community
Participate
Working Groups
We are in the process to move the textview unit tests to the orion test framework. Unfortunately, besides Bug344344#c7, we are also having trouble with our async tests. The framework will essentially start all the tests in the suite at the same time, and try to run them in parallel. This is a big problem because tests can share data. In our case, the view. For example, take the pageDown and the pageUp test. They both scroll the same view and they are both async (they need to return the control to the ua after each operation). The correct behavior is to run all async operations for the pageDown first, then run all the async operations for the pageUp. The current implementation alternates pageDown,pageUp operations never ending. Note that jstestdrive does solve this problem: "The test runner will not execute any subsequent step in the queue until all outstanding callbacks of the current step are complete. If the callbacks are not a called for an egregious amount of time, currently set to 30 seconds, the test fails. " http://code.google.com/p/js-test-driver/wiki/AsyncTestCase Note that changing our tests to not share the view is not ideal, running performance tests in parallel is wrong.
Fixed.
