...
Open outputfiles
If the case declare some outputfile output file it is opened to show its content
...
Graph cases along the time
It read the logs and show graphs along time of the tests, with memory and time consumption of if fail or not, to detect the moment when a change of the code modify its performance or robustness
It show just the points of the graph belonging to tested cases
Graphs joined along the time
Similar to the previous, but in this case is show a single graph of the multiple selection, interpolating and averaging values in order to have the same x-time.
Export project selection
It write to a new folder a new xml project with only the selected test cases, and also copy only the batch files of these cases, and the models related in the batch files (e.g. to run a range of cheaper tests in a Bitbucket pipeline)
Analize fail cause
Experimental option that require visual studio and a git repository configured to allow export from git a history of versions, compile and test automatically in order to try to find the git commit that is responsible of the error.
Analize if random
Experimental option that run the cases several times and if its results have some difference set the case as random (it the result must be deterministic a random result is considered as an error, very difficult to be found)
Copy case ids to clipboard
Copy the hash ids of the selected cases to the clipboard, to facilitate scripting test on the lower command line, or to send to other users the list of cases of interest
Help field
Show in a window the text of the ‘help’ fields of the selected cases (this help field is expected to be filled with an optional short explanation of why is this test created)