Unscripted testing VSI

[Nick Draper]

See the items at the bottom of this page http://www.mantidproject.org/Unscripted_Manual_Testing

Record in the comments what environment was used

[Nick Draper]

Opened straight to testing with a fake owner, so anyone can test.

[Owen Arnold]

I'm going to be testing this on Windows 7 x64

[Owen Arnold]

All looks good apart from this #6436. Everything else seems to work fine.

[Nick Draper]

Ticket resurrected for R2.6

[Michael Reuter]

On Windows 7 64bit using Mantid kit version 2.5.1961 both the VSI and ParaView components pass all of my testing.

[Michael Reuter]

On OSX Mountain Lion using Mantid kit version 2.5.1960 both the VSI and ParaView components pass all my testing.

[Michael Reuter]

On RHEL6 using Mantid kit version 2.5.1960 the VSI passes all my testing. ParaView fails, but unfortunately, is expected.

[Michael Reuter]

On Ubuntu 12.04 using Mantid kit version 2.5.1960 both the VSI and ParaView components pass all of my testing.

[Michael Reuter]

I feel confident that things are working under normal circumstances on all platforms. No bets on the beta testers though. :-)

[Nick Draper]

Reopened for testing in Release 3.0

[Michael Reuter]

Discovered #8257 during testing.

[Michael Reuter]

On OSX Mountain Lion using Mantid kit version 2.6.20131028.1710 both the VSI and ParaView components pass all my testing.

[Michael Reuter]

On Windows 7 64bit using Mantid kit version 2.6.20131030.55 both VSI and ParaView components pass all of my testing.

[Michael Reuter]

On RHEL6 using Mantid kit version 2.6.20131030.2123 the VSI passes all of my testing. ParaView fails as before. Sigh.

[Michael Reuter]

I'm having trouble getting the Ubuntu kit to recognize ParaView like I was able to do last release.

[Michael Reuter]

The ParaView components seem to work just fine, but Mantid can't seem to execute ParaView on the initial setup. This looks very weird.

[Michael Reuter]

I still can't get the Ubuntu package to work correctly. However, I'm signing off since the majority of the platforms work.

[Nick Draper]

Reactivated for release 3.1

[Michael Reuter]

On OSX Mountain Lion using Mantid kit version 3.0.20140203.2142 both the VSI and ParaView components pass all my testing.

[Michael Reuter]

On Ubuntu 12.04 using Mantid kit version 3.0.20140204.1824 both the VSI and ParaView components pass all my testing.

[Michael Reuter]

On RHEL6 using Mantid kit version 3.0.21040203.2142 the VSI passes all of my testing. ParaView fails as before.

[Owen Arnold]

Tested on Windows x64. Managed to invoke some edge cases, but vast majority of functionality is stable. Kit used for testing was mantid-3.0.20140205.1858-win64.exe. #8897 contains steps to cause issue mentioned.

[Michael Reuter]

Thanks Owen. Looks like we are good to go.

[Nick Draper]

Reasurrected for R3.3 testing

[Roman Tolchenov]

Tested on Window. Generally it is working fine. A few minor issues in #10783. The crash from #8460 is still there.

[Owen Arnold]

Test the VSI, not VATES, VATES is the project name.

[Federico M Pouzols]

Tested this morning's master on Windows and debian. I only found very minor issues, and confirmed a few old minor issues already know.

Conclusion:

• All dialogs and actions seem to behave well, including the recent CutMD which I tested on the surface but with pretty wild inputs.

Old and new issues:

• On the tab "Properties", the "?" button (on the right of "X Delete") does nothing, at least for the example data sources that I used (MDHisto, MDEvent, Peaks workspaces). I added this to ticket #10783.

• I got a crash on windows, while on the 'three slice view' when I clicked on 'Edit' (in Properties - Coloring) and then changed the "Nan Color" (in Color Map Editor - Color Mapping Parameters), after clicking OK in the color selection dialog. However, I cannot reproduce it.

• About the crash first reported in #8460, it seems that the present behavior is that the source is removed? If so, this ticket would have become invalid. I could only check on Windows and debian, but I'd assume that this behavior is not platform dependent.

About the minor issues that were detected in the previous iteration unscripted testing (#10783):

1. "Dialogs hide VSI behind MantidPlot. This happens for example with View->Settings", both on Windows and linux.
2. "ThreeSlice: slices can rotate (middle button). Reset tool button doesn't cancel the rotation".
3. "View settings General page... colours..." I think this is much better now, there's a 'Color Palette' tab and it shows very clearly what colors apply to what (Surface, foreground, edges, etc.)
4. "View settings General page..." - I couldn't find the "Use Parallel Projection" checkbox, has this been removed in the newer ParaView version used now?
5. "Axis Label Color doesn't stay set to the custom value...". I tried changing the color of the 'cube axis' and yes, when you switch from normal to another view and back to normal, the axes are lost and the view starts from the default position and angle. But I guess that this is a more general issue (or maybe intended behavior) when switching back to any of the views.
6. "Zoom to Box..." It seems to work after several zooms in a row, but I think it doesn't zoom to the selecte box, but to a wider view?

[Stuart Campbell]

This ticket has been transferred to github issue ​7253