[forge-issues] [JBoss JIRA] (FORGE-2144) Adding powermock rule into the test will cause forge to be unable to find it

George Gastaldi (JIRA) issues at jboss.org
Fri Feb 13 10:09:49 EST 2015


    [ https://issues.jboss.org/browse/FORGE-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040189#comment-13040189 ] 

George Gastaldi edited comment on FORGE-2144 at 2/13/15 10:09 AM:
------------------------------------------------------------------

This is because this dependency is not explicitly added in the @Deployment method


was (Author: gastaldi):
This is because this dependency is not explicitly added to the @Deployment method

> Adding powermock rule into the test will cause forge to be unable to find it
> ----------------------------------------------------------------------------
>
>                 Key: FORGE-2144
>                 URL: https://issues.jboss.org/browse/FORGE-2144
>             Project: Forge
>          Issue Type: Bug
>            Reporter: Matej Briskar
>
> Powermock is a framework for mocking static methods (this is a tricky thing to do). By default you will run it using @RunWith annotation, however since the arquillian has it's own @RunWith(Arquillian.class) annotation, it provides an option to use the mocking using the junit.Rule. This, however, makes the tests fail.
> The difference is in the  registry.getExportedInstance() for the _DEFAULT_ addon. In one it returns the class, in the other it does not.
> Recently, there was added another way of running the powermock along arquillian using java agent, even though it is not easy to make this work, it looks it fails on same error.
> Error:
> java.lang.IllegalStateException: Test runner could not locate test class [org.jboss.windup.rules.java.NotUnzippableFileTest] in any deployed Addon.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


More information about the forge-issues mailing list