How to use CDI and before/after with UI tests?

[chschulz]

Hello,

I am wondering if there is a way to use CDI in UI tests to be able to generate and delete test data in corresponding test phases.

I have tried following code. It makes no difference if I am using the @RunAsClient annotation on class or method level.

Is the only method to autogenerate data a Startup Bean or similar?

The injected bean is null if it is called in before/after.

@RunWith(Arquillian.class)
public class ListControllerUiTest {
  @Drone
  private WebDriver browser;


  @Inject
  private TestDataProvider dataProvider;


  @Deployment
  public static WebArchive createDeployment() {
    ...
  }


  @Before
  public void insertData() {
    dataProvider.insertData(); // NPE
  }

  @After
  public void clearData() {
    dataProvider.clearData(); // NPE
  }


  @Test
  @RunAsClient
  public void showList(@InitialPage final ListPage page) {
    ...
  }

[mjobanek]

Hi,

the injection doesn't work because the methods are run on a client, not in a container. The rule for junit is:

The whole test class or at least one of the test methods is intended to be run on a client => before/after methods are invoked on a client (CDI is NOT supported)

The whole test class (including all test methods) is intended to be run in a container => before/after methods are invoked in a container (CDI is supported)

You could use ShrinkWrap to add a servlet into your deployment that will insert and clean the data. Then it would be possible to call this servlet in before/after methods running on a client.

There is another workaround, but very complicated and not nice - replace before/after methods by test methods running in a container and launch the test methods in a appropriate sequence.

Best

Matous

[bmajsak]

There is also another way to achieve before/after behaviour but that would lead you to implement your own extension and pass commands to Arquillian through CommandService. If you are brave enough to follow this path I can give you some pointers

Cheers,

Bartosz

[chschulz]

Sounds interesting. I would try to achieve that approach.

[bmajsak]

Cool, let me prepare some gists. Will do it this evening

Cheers,

Bartosz

[chschulz]

Any news on this? I would like to start with the extension.

[bmajsak]

Got stuck with other stuff :\ Sorry for that.

Give me few more days, I will share something on github. I don't want to point you to some bigger example (like in Arquillian Persistence Extension), as this might require getting a bit bigger context of the given extension.

[mjobanek]

Hi guys,

with the new version of the arquillian-core, there is one new possibility - to use a JUnit rule for that. see Arquillian Core 1.1.11.Final Released · Arquillian Blog

The rule will be launched on both the client side and in a container (depends on which method is going to be run).

[chschulz]

Sounds great, but it seems that there is an issue with the warp extension, see NullPointerException in ProxyUsageTracker with Warp and recent version of Universe and using ExpectedException Rule.

Furthermore I am wondering how to write a JUnit rule which is only applied in the container during the before phase.

[mjobanek]

Looking at the dependency tree - there seems to be some older version...

[chschulz]

Please answer in the other thread and tell me which dependency is older.

Furthermore I am wondering how to write a JUnit rule which is only applied in the container during the before phase.How to use CDI and before/after with UI tests?

Is there any annotation or similar to do this?

[mjobanek]

Answered... BTW, the exception should not have any impact on using @Rule in your tests (if you are using TestRule or MethodRule).

Yeah, you are right that you cannot force JUnit rule to be run only in the container - in the case of in-container test method it is run on both sides.

[mjobanek]

Similar discussion: Re: JUnit Rules execution