Problem when starting a test without a Selenium driver set

[simone36050]

If a user runs a test without setting a Selenium driver, the test will fail because the driver cannot be used. The user will then probably select the correct driver and re-run the test. The result is that the test may not run correctly. In particular, in multi-session tests where the instructions of the first session are supposed to sleep until the second session reaches a specific instruction, the sleep function is not performed correctly.

Steps to reproduce:

• run Burp with MIG-T;
• choose the wrong driver file;
• import test and sessions (for my tests, I used OP-Token response-refresh_token-already-used.json);
• run the test;
• select the correct driver;
• re-run the test;
• wait for the end.

Expected result: pass
Actual result: not applied

[mattebit]

I added the PR above, it basically add a more complex verification to the selection of the executable before allowing the user to use it. This partially solves the initial problem of using a wrong executable during test executions. I was not yet able to identify where the second issue originates, I will do it.