Runs performance tests of the rigid body physics engine. See
2D Physics Engine Overview. Each test has an expected time, if it
takes significantly longer then a failure is reported.
The function test/TestRig.getPerfLimit contains the
policy for 'how much longer than expected is a failure'.
The expected time for each test is dependent on the particular machine that the test is
being run on, as well as the browser. The expected running time for the performance
tests are specified in test/ExpectedPerf.ExpectedPerf. There is a separate
number there for each combination of machine, browser, and test.
machine name See test/TestRig.getMachineName to learn
how to specify the unique name of your particular machine in the file MachineName.js.
If MachineName.js doesn't exist, then the performance tests will use large default
values for the time limit so that no errors are reported.
To run the performance test on devices like iPhone or android where we don't have
control over the file system: select machine name from a menu, and save that machine
name choice in HTML5 local storage. Steps needed to do this:
Retrieve the machine name from local storage (this might do away with the
MachineName.js file)
Provide a menu of machine name choices gathered from ExpectedPerf. Selecting from the
menu will store that name in local storage (and perhaps reload the page or re-run the
test).
Runs performance tests of the rigid body physics engine. See 2D Physics Engine Overview. Each test has an expected time, if it takes significantly longer then a failure is reported. The function test/TestRig.getPerfLimit contains the policy for 'how much longer than expected is a failure'.
The expected time for each test is dependent on the particular machine that the test is being run on, as well as the browser. The expected running time for the performance tests are specified in test/ExpectedPerf.ExpectedPerf. There is a separate number there for each combination of machine, browser, and test.
machine name See test/TestRig.getMachineName to learn how to specify the unique name of your particular machine in the file
MachineName.js. IfMachineName.jsdoesn't exist, then the performance tests will use large default values for the time limit so that no errors are reported.browser name The browser name comes from test/TestRig.getBrowserName.
test name The test name is usually the name of the test function such as
six_blocks_perfforStraightStraightTest.six_blocks_perf().To Do: Menu of Machine Names
To run the performance test on devices like iPhone or android where we don't have control over the file system: select machine name from a menu, and save that machine name choice in HTML5 local storage. Steps needed to do this:
Retrieve the machine name from local storage (this might do away with the MachineName.js file)
Provide a menu of machine name choices gathered from ExpectedPerf. Selecting from the menu will store that name in local storage (and perhaps reload the page or re-run the test).