We developed selenium cases in a weird way that we finally had two @StveWedriver annotations, one in an abstract layer and one in the actual test case (extending that abstract class).
Yeah, it was a bad implementation
but would it be possible to check the number of fields (in the DriverModule) and throw a warning so this is more visible ?
The consequence was that several developers had to work on it, the tests were succeeding but at the end it would throw an UnreachableBrowserException.