UnitTest SANS2D gui interaction

[Gesner Passos]

Although we do not have GUI unit tests, this ticket is to create a unit test that check that all the call and executions that SANS INTERFACE does through the ReductionSingleton() is available and correct.

It is implemented as unit test because it is fast, and will require just one file, that can be created on fly.

[Gesner Passos]

re #8341: SANS2D Gui Settings unit test

Changeset: 564ac091a4067872f9ad72889ece6080caff8889

[Gesner Passos]

re #8341: add SANS2D Gui Settings unit to cmakelist

Changeset: f00c2baefd8ff880bdb6cc608ec5bbed955fd56c

[Gesner Passos]

re #8341: add MaskFile for SANS2D Gui Settings unittest

Changeset: ca83a254996dd6432197cb3c5b86b0d72220bfca

[Gesner Passos]

Tester:

These tests cover the usage of SANS Interface Settings tab. It ensures that all the executions and readings from that Tab responds as expected. Unfortunately, MaskFile command still requires a file as input. It would be great to have it accepting also "File, filename, or generator to read", these would allow us to remove the file loading part. I will add it as a new ticket #8406. But, to convince you to let this pass (it took 1.52 seconds to execute). The mean time for all the unit tests are 0.96 seconds with a standard deviation of 1.8. So, it is inside a good margin.

If you agree with me, and is convinced that the unit test provide good benefit (code review). Than, you may let it pass. (It has passed on all machines by now).

[Peter Parker]

Merge remote-tracking branch 'origin/feature/8341_sans_gui_unittest'

Full changeset: ​03621162f71031fd7c4cca2cc948ec6cae3be22c

[Peter Parker]

Looks good. Your stats have convinced me - it is fine being a unit test!

[Peter Parker]

(In #8308) See updated ticket description, and ignore previous comment from Gesner.

[Stuart Campbell]

This ticket has been transferred to github issue ​9187