Hi everyone, I need to use Powermock to suppress static initialization of some classes used by my JBehave tests. Currently the tests are executed by using the run-as-embeddables goal of the maven plugin.
Have tried just adding the @RunWith(PowerMockRunner.class) to the existing stories that extend JUnitStory with no success. Have tried removing the maven plugin dependency and embedding the stories in standard JUnit tests that is then executed by Surefire. This works as far as PowerMockRunner goes, but for some reason result in some test failures. These same test failures also happen when I upgrade the jbehave core from the current 3.1.2 to 3.6.9. I did not write the stories, they are very complex and I don't know if these failures with newer jbehave versions are due to the specific tests being faulty or not. Is there a way that I can introduce PowerMockRunner into the equation while still using the Maven jbehave plugin and version 3.1.2 of jbehave? Regards, Alwyn Schoeman
