Improve test coverage about webdriver-classic-driver

[stof]

I think this might be a mix of both.

The error handling for start and stop should be covered in custom tests (as the failure modes there are specific to each driver).
The error handling of getWebdriver should as well because the DriverInterface makes it an undefined behavior to call methods on a non-started driver. It does not require getting a DriverException in such case.

Other cases might correspond to holes in the coverage of invalid usages in the shared testsuite (for instance, we added testing for some invalid form field value types among the latest improvements of that testsuite). Those should be implemented in the shared testsuite to improve coverage in all drivers.