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

Introduce a cathegory of TestAlgorithm for algorithms used in testing and include appropriate algorithms there #11393

Closed
abuts opened this issue Nov 13, 2014 · 3 comments
Assignees
Labels
Framework Issues and pull requests related to components in the Framework Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@abuts
Copy link
Member

abuts commented Nov 13, 2014

This issue was originally TRAC 10551

I am writing this ticket straggling again to remember and identify an algorithm appropriate for creating a testing workspace.

I think, creating a category of Testing algorithm and gathering these algorithms together in Mantid documentation for further references would greatly simplify such job in a future.

@abuts
Copy link
Member Author

abuts commented Dec 8, 2014

@abuts (2014-11-13T13:36:59):
refs http://trac.mantidproject.org/mantid/ticket/10551 This is the group I think used for tests most intensively

fc23f66


@abuts (2014-11-13T13:41:31):
Though I thought the commit above will fix it, I've find out how it all was implemented in Mantid realized that a classification can be a most debated topic which nobody would agree.

Leaving for the assigner to decide if this ticket is feasible& reasonable.


@NickDraper (2014-12-08T10:25:38):
Moved to the backlog at the code freeze of R3.3

@abuts abuts added the Framework Issues and pull requests related to components in the Framework label Jun 3, 2015
@abuts abuts self-assigned this Jun 3, 2015
@stale
Copy link

stale bot commented Feb 24, 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 24, 2021
@stale
Copy link

stale bot commented Mar 3, 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 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues and pull requests related to components in the Framework 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

1 participant