Unable to Inject into Test Class

[mbarkley]

I'm currently migrating a plugin from version 1.4.4.Final to 2.0.0.CR2 of Forge, and injection is not occurring with my new tests using furnace.

Here is the test. Here is my pom. And here is the terminal output while running the test.

The result is that the test fails because both of the @Inject'ed fields are null. I've tried looking at tests in the Forge repository, but I have been unable to discern what I am doing differently.

Any help is appreciated.

[lincolnthree]

Let's talk about this in the #forge IRC channel

On Wed, Jan 29, 2014 at 10:42 AM, <[e-mail]> wrote:

I'm currently migrating a plugin from version 1.4.4.Final to 2.0.0.CR2 of

Forge, and injection is not occurring with my new tests using furnace.

Here (

https://github.com/mbarkley/forge-errai/blob/f91679f2e549cefa457ba0bdca0ee35d41a2965b/src/test/java/org/jboss/errai/forge/test/base/ForgeTest.java)

is the test. Here (

https://github.com/mbarkley/forge-errai/blob/f91679f2e549cefa457ba0bdca0ee35d41a2965b/pom.xml)

is my pom. And here (http://pastebin.com/D4J3MW3G) is the terminal output

while running the test.

The result is that the test fails because both of the @Inject'ed fields

are null. I've tried looking at tests in the Forge repository, but I have

been unable to discern what I am doing differently.

Any help is appreciated.

Posted by forums

Original post: https://community.jboss.org/message/855384#855384

_______________________________________________

forge-users mailing list

[e-mail]

https://lists.jboss.org/mailman/listinfo/forge-users

--

Lincoln Baxter, III

http://ocpsoft.org

"Simpler is better."

[mbarkley]

Hey Lincoln,

I ended up getting the test to work. For the record, here is the result I ended up with (ignore the classes added to the deployment -- those were required to get other test classes extending ForgeTest to run).

Note that the last step that was required to get injection working was to remove the name (previously "ForgeTest") from the @Deployment annotation. It is possible to reproduce the failure by checking out a copy of the linked commit, adding "ForgeTest" as the name of the @Deployment, and running ForgeTest with JUnit.

[lincolnthree]

Hey Max,

Interesting. I'm willing to bet this has something to do with the naming

requirements e.g: "groupId:addonId". I'll have to fix this in our

test-runner. Thanks for reporting the fix!

~Lincoln

On Thu, Jan 30, 2014 at 9:13 AM, <[e-mail]> wrote:

Hey Lincoln,

I ended up getting the test to work. For the record, here (

https://github.com/mbarkley/forge-errai/blob/c523efb2c1a114275a8fc8492bbcdd03d126bff4/src/test/java/org/jboss/errai/forge/test/base/ForgeTest.java)

is the result I ended up with (ignore the classes added to the deployment

-- those were required to get other test classes extending ForgeTest to

run).

Note that the last step that was required to get injection working was to

remove the name (previously "ForgeTest") from the @Deployment annotation.

It is possible to reproduce the failure by checking out a copy of the

linked commit, adding "ForgeTest" as the name of the @Deployment, and

running ForgeTest with JUnit.

Posted by forums

Original post: https://community.jboss.org/message/855522#855522

_______________________________________________

forge-users mailing list

[e-mail]

https://lists.jboss.org/mailman/listinfo/forge-users

--

Lincoln Baxter, III

http://ocpsoft.org

"Simpler is better."