Slow Unit Tests - LoadEventNexusTest

[OwenArnold]

This issue was originally TRAC 10151

This ticket is blocked by :

• TRAC10471

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 ==

1. Test suits (each test class instance) '''should execute in < 1 second''' as a rough target
2. As a corollary to the above, If the test suite contains lots of test methods aim for '''< 0.1 second per test method'''
3. 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 ==

1. '''Keep tests readable and improve code readability where possible. Unit tests are documentation.'''
2. Do not delete test methods without good reason. We do not want to reduce test coverage
3. Changing the algorithm code to improve speed is OK, but exercise caution. Add additional test coverage if it's not already good enough.
4. 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.
5. Most of the speed improvements will probably come from better selection of input data. Caching input data is also a good option.
6. 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.

Russell Taylor had previously worked on this, but the tests are still taking 14 seconds to run.

---

Keywords: Maintenance

[OwenArnold]

@OwenArnold (2014-11-19T14:15:49):
Not realistically going to get done for the 3.3 release. This is however linked to the work that Owen and Pete have done (are doing) the ground work for in http://trac.mantidproject.org/mantid/ticket/10471

---

@NickDraper (2015-04-27T08:10:34):
Moved to R3.5 at the R3.4 code freeze

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

[stale]

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.