Bug: Browser is not started for @After method if it's declared in different class than the test itself #322
Labels
bug
codeReadyForMerge
The issue was implemented and the branch is ready to be reviewed and merged into develop
Quick Description
With the feature to start new browser for @after method if needed, we introduced this bug. Is seems that the reason is that we use method.getDeclaredClass() call to get the class to search the after methods in. Instead, we should use the actual test class that gets passed to this method.
Actual Behaviour
If @after method is declared in different class than the test itself, no webdriver is available in the method
Expected Behaviour
Test browser should be available for all @after methods, if nothing different is configured
Taks
The text was updated successfully, but these errors were encountered: