Manual Testing Error Reporter

[sf1919]

You have been assigned manual testing. The hope is to catch as many problems with the code before release, so it would be great if you can take some time to give a serious test to your assigned area. Thank you!!

The general guide to manual testing:

• The tests must be performed on the installer versions of the final release candidate. Not on local compiled code.
• Serious errors involving loss of functionality, crashes etc. should be raised as issues with the current release as a milestone and an email sent to the project manager immediately.
• Minor and cosmetic issues should be raised as issues against the forthcoming releases.
• First try things that should work, then try to break Mantid, e.g. entering invalid values, unexpected characters etc.
• Don't spend more than a few hours on the testing as fatigue will kick in.
• If you find errors in the documentation, please correct them.
• Comment against this ticket the OS environment you are testing against.
• Close the this issue once you are done.

Specific Notes:

http://developer.mantidproject.org/Testing/ErrorReporter-ProjectRecovery/ErrorReporterTesting.html

[jhaigh0]

Segfault algorithm is not crashing Mantid on Mac

[jhaigh0]

Need to investigate possibility of error report send resulting in status 0.

[jhaigh0]

Need to update instructions to include testing the character limit label I added

[martyngigg]

@jhaigh0 Could you creates issues for the things we found so that we can close the testing as complete?

[jhaigh0]

Created Issues #35008 and #35010. The one about the 0 status is a false alarm, I think. - I didn't realise the PR about the error reporter remaining open hadn't been merged in, and looking at the code, it will be able to handle a 0 status code if that does occur.