Provide unit tests for samples and scripts creation and execution

[ascheibe]

Previously, all samples unit tests were added to the class SamplesTest. For maintainability reasons and to locate the corresponding unit test faster, each sample should have its separate unit test class. Additionally, the scripts provided on the StartPage of the Optimizer should also have a unit test for automated detection of API changes.

TODO:

• Split SamplesTest class into individual classes
• Create UnitTests for Script creation and execution

[ascheibe]

Please assign this ticket to jkarder after you have implemented your tests.

[bburlacu]

r11450: Separated samples class into separate test classes. Added scripts unit tests (grid search classification/regression).

[bburlacu]

r11466: Updated grid search start page scripts and unit tests, which now reside in HeuristicLab.Scripting and belong to test category "Scripting".

[jkarder]

Be advised that the CSharpScript.Execute method creates and starts a thread in which the script is actually executed. If you check the variable store immediately after starting the script, you most likely will not be able to retrieve any results since the script execution might not have finished yet. For now you can register an event handler on ScriptExecutionFinished and use e.g. a ManualResetEvent to synchronize the script and unit test execution.

[abeham]

I would opt that we call it ExecuteAsync and have a synchronized Execute method. A similar change was already identified for algorithms in HL as well.

[bburlacu]

r11483: Updated script unit tests to wait for the script thread to finish before validating results.

[jkarder]

r11514:

• updated/added unit tests
  • added AssemblyInitialize method to load all plugins, create output directories for (script) samples and initialize the MainForm
  • script code is now stored in test resource files
  • refactored unit tests
• updated (script) samples
• added Test.cmd

[jkarder]

@bburlacu: I oriented myself towards the sample unit tests and created additional unit tests for the script sample generation. I will reassign you this ticket after a successful build so you can tune the SVM parameters of your samples.

[jkarder]

r11515: changed my mind about testing ui code

[bburlacu]

r11890: Adjusted parameters ranges in the random forest grid search tests and fixed unit tests to match the new results.

[jkarder]

r11907: merged r11450, r11466, r11483, r11514, r11515 and r11890 into stable: merged r11450, r11466, r11483, r11514, r11515 and r11890 into stable