[jbosstools-issues] [JBoss JIRA] (JBIDE-18265) NullPointerException in ArquillianBuilder when creating test class with the name Test
Snjezana Peco (JIRA)
issues at jboss.org
Mon Oct 6 10:00:13 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-18265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Snjezana Peco resolved JBIDE-18265.
-----------------------------------
Resolution: Done
The patch is only included in master.
> NullPointerException in ArquillianBuilder when creating test class with the name Test
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18265
> URL: https://issues.jboss.org/browse/JBIDE-18265
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.2.0.CR1
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.3.0.Alpha1
>
>
> When I try to create an Arquillan test class with the name Test, it is created, however, the Arquillian builder fails with NP.
> {code}
> java.lang.NullPointerException
> at org.eclipse.jdt.core.dom.MethodBinding.filterTypeAnnotations(MethodBinding.java:205)
> at org.eclipse.jdt.core.dom.MethodBinding.getAnnotations(MethodBinding.java:104)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.isDeploymentMethod(ArquillianSearchEngine.java:862)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.getDeploymentMethods(ArquillianSearchEngine.java:849)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.hasDeploymentMethod(ArquillianSearchEngine.java:599)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:255)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:210)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:109)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> This is because the test method is generated with the @Test annotation without fully qualified name.
> {code}
> @Test
> public void test() {
> fail("Not yet implemented");
> }
> {code}
> In JUnit, when I tried to create test class with the name Test, the @Test annotation was generated with fullly qualified name
> {code}
> @Test
> @org.junit.Test
> public void test() {
> fail("Not yet implemented");
> }
> {code}
> However, when I checked that I want do generate tearDown method, JUnit created the annotation withou fully qualified name too.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
More information about the jbosstools-issues
mailing list