Slow Unit Tests for Sam Jackson #10746
Labels
Framework
Issues and pull requests related to components in the Framework
Maintenance
Unassigned issues to be addressed in the next maintenance period.
Milestone
This ticket is blocks : TRAC9905
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 ==
== 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.
Keywords: Maintenance
The text was updated successfully, but these errors were encountered: