New answers tagged junit
I think the same scenario could happen even if class A uses class B but does not contain class B. One way to mitigate that risk is to write unit tests for class B that validate the assumptions embedded in your mock.
Because you are using the tags (@Chrome and @Firefox) at the beginning of your feature file (Feature). And both of them will be executed for each scenario. Another solution is to switch between the browsers via your job configurations and system property i.e. each job executes some scenarios for a specific browser. For example: @Before("@web") public ...
Top 50 recent answers are included