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
Improve unit test for ConvertToMatrixWorkspace #2899
Comments
@NickDraper (2010-12-16T09:49:26): @NickDraper (2011-02-15T09:09:32): @NickDraper (2011-04-27T07:36:00): @NickDraper (2011-09-19T09:30:53): @NickDraper (2012-01-09T09:43:30): @NickDraper (2012-04-30T14:14:07): @NickDraper (2012-08-10T12:44:01): @NickDraper (2012-10-28T11:39:14): @NickDraper (2013-01-28T09:23:24): @NickDraper (2013-04-29T09:50:01): @NickDraper (2013-07-26T13:55:02): @NickDraper (2014-02-14T11:07:56): |
Add unit test to ConvertToMatrixWorkspaceTest that shows that the histogram representation of an event workspace matches that of the histogram in the created MatrixWorkspace from this algorithm |
It would seem that this has been done at some point. However, the test can still be improved. It uses a file and that can be removed in favour of an in-memory workspace. |
Changed header file to use in-memory workspace instead of file Refs #2899
Reduced dependencies on name spaces and ordered header files to comply with coding standards Refs #2899
Removed any redundant includes from ConvertToMatrixWorkspace.h. Changed any use of AnalysisDataService to use Mantid::API::Algorithm instead Reformatted using Clang format
forgot to do this before formatting with clang
Changed from TS_ASSERT_EQUALS to TSM_ASSERT_EQUALS and involved the loop variant in the failure message to identify which Histogram produced the error.
Convert int to string in such a way that RHEL6/7 are happy with the conversion
This issue was originally TRAC 2052
At the moment the test is just a copy of
CloneWorkspace()
, it really needs to test that the histogram representation of an event workspace is being copied out correctly.Keywords: Maintenance
The text was updated successfully, but these errors were encountered: