Ticket #9899 (closed: wontfix)
Slow Unit Tests for Martyn Gigg
Reported by: | Owen Arnold | Owned by: | Martyn Gigg |
---|---|---|---|
Priority: | major | Milestone: | Release 3.3 |
Component: | Framework | Keywords: | Maintenance |
Cc: | Blocked By: | ||
Blocking: | #9905 | Tester: | Owen Arnold |
Description (last modified by Owen Arnold) (diff)
We have a number of slow running unit tests which we need to fix as part of the 3.3 maintenance window. We are targeting test suits than execute in > 2 seconds on our clean rhel6 build servers. For IO tests (Loading & Saving) we have applied a more generous threshold of > 5 seconds.
See the full list to see which tests have been assigned to you: http://www.mantidproject.org/images/2/2f/Slow_tests.xlsx_-_Sheet1.pdf
Criteria
- Test suits (each test class instance) should execute in < 1 second as a rough target
- As a corollary to the above, If the test suite contains lots of test methods aim for < 0.1 second per test method
- If for some reason you get the speed up the test below the target using the strategies listed below, you need to justify why when you close the ticket.
Guidelines/instructions to help
- Keep tests readable and improve code readability where possible. Unit tests are documentation.
- Do not delete test methods without good reason. We do not want to reduce test coverage
- Changing the algorithm code to improve speed is OK, but exercise caution. Add additional test coverage if it's not already good enough.
- Take test methods that are slow and involve IO, or are processor intensive and make them into system tests. Integration tests are not Unit tests.
- Most of the speed improvements will probably come from better selection of input data. Caching input data is also a good option.
- Create sub tickets for algorithms or groups of algorithms to help testability if you wish, but mark this ticket as the 'blocked' by each one.
Change History
comment:1 Changed 6 years ago by Owen Arnold
- Owner changed from Nick Draper to Martyn Gigg
- Status changed from new to assigned
- Description modified (diff)
- Summary changed from Slow Unit Tests for Nick Draper (cloned) to Slow Unit Tests for Martyn Gigg
comment:4 Changed 6 years ago by Martyn Gigg
- Status changed from inprogress to verify
- Resolution set to wontfix
It looks like the changes in #9740 have decreased all of these tests below the required 2s threshold. The speeds of the tests, on the last clean develop build, marked against my name are:
- AlgorithmManagerTest - 1.2s
- FrameworkManagerTest - 1.4s
- ResolutionConvolutionCrossSectionTest - 35ms
I don't think it's worthwhile doing anything else on the code relating to this.
comment:5 Changed 6 years ago by Owen Arnold
- Status changed from verify to verifying
- Tester set to Owen Arnold
comment:6 Changed 6 years ago by Owen Arnold
- Status changed from verifying to closed
Agreed. There has been a speedup. Would be nice if some of these tests ran in < 1 second, but not worth the effort, and in some cases would be impossible on RHEL6 anyway, based on the issues we have seen around OMP loop thread creation.