Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement tests for the calibration modules #11002

Closed
martyngigg opened this issue Aug 22, 2014 · 3 comments
Closed

Implement tests for the calibration modules #11002

martyngigg opened this issue Aug 22, 2014 · 3 comments
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@martyngigg
Copy link
Member

This issue was originally TRAC 10160

There are no tests for the calibration modules and as a result they have broken without anyone being aware of it.

We should implement unit tests, or if they can't be run fast enough, system tests for the modules under Code/Mantid/scripts/Calibration.

@martyngigg
Copy link
Member Author

@martyngigg (2014-08-22T12:08:47):
(In http://trac.mantidproject.org/mantid/ticket/10159) Note: http://trac.mantidproject.org/mantid/ticket/10160 has been created to implement tests for these modules.


@NickDraper (2014-12-18T15:35:27):
Moved to R3.4


@NickDraper (2015-05-12T14:03:07):
Moved to R3.5 at the end of R3.4

@martyngigg martyngigg added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Python labels Jun 3, 2015
@martyngigg martyngigg added this to the Release 3.5 milestone Jun 3, 2015
@NickDraper NickDraper modified the milestones: Release 3.5, Release 3.6 Sep 14, 2015
@NickDraper NickDraper modified the milestones: Release 3.6, Release 3.7 Jan 22, 2016
@NickDraper NickDraper modified the milestones: Release 3.7, Release 3.8 May 20, 2016
@gemmaguest gemmaguest removed the Python label Jul 29, 2020
@stale
Copy link

stale bot commented Feb 22, 2021

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 stale bot added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Feb 22, 2021
@stale
Copy link

stale bot commented Mar 1, 2021

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.

@stale stale bot closed this as completed Mar 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
None yet
Development

No branches or pull requests

4 participants