Annotation Processors not working in java 10/11

[paulsjohnson91]

In java 10 and 11, lazy objects are initializing.

Expected Behavior

@Page
private ExamplePage examplePage;

goTo(examplePage)

@page object should initialize and FluentLenium should go to the page

Current Behavior

examplePage is null so is throwing a NullPointerException.

This also happens with lazy locators with @findby

Context (Environment)

Tried with both Java 10 and 11 on FluentLenium version 3.7.0

[koryl]

Thank you for your feedback! FluentLenium was checked mainly for jdk8 and I will try to find the reason for such behavior in newer versions. It is important for us to bring FL to the upcoming Java 11.

[filipcynarski]

Looks like it works :) Could you please check w/ 4.0.0 release?

[paulsjohnson91]

Unfortunately I'm still getting the same issues as before.

java.lang.IllegalArgumentException: Page is mandatory

The annotators are not initialising the page objects.

Checked on version 4.0.0. with Java 11

[slawekradzyminski]

@paulsjohnson91 Can you please share complete class code?

[paulsjohnson91]

`
private final String BO_USERNAME = prop("operatorUserName");
private final String BO_PASSWORD = prop("operatorPassword");

@page
private LogInPage logInPage;

@page
private DashboardPage dashboardPage;

@before
public void before(Scenario scenario) {
super.setUpBefore(scenario);
}

@after
public void after(Scenario scenario) {
super.tearDownAfter(scenario);
}

@given("^the operator navigates to back office login page$")
public void the_operator_navigates_to_back_office_login_page() {
goTo(logInPage);
logInPage.isAt();
}
`

[slawekradzyminski]

@paulsjohnson91 please copy/paste everything with imports. That would be helpful :)

[paulsjohnson91]

`
package com.backoffice.whgtf.test.bnw.steps.ui.auth;

import static com.backoffice.whgtf.test.bnw.util.PropertyHelper.prop;

import com.backoffice.whgtf.test.bnw.steps.AbstractCucumberTest;
import com.backoffice.whgtf.test.bnw.ui.pom.backoffice.page.DashboardPage;
import com.backoffice.whgtf.test.bnw.ui.pom.backoffice.page.auth.LogInPage;
import cucumber.api.Scenario;
import cucumber.api.java.After;
import cucumber.api.java.Before;
import cucumber.api.java.en.Given;
import cucumber.api.java.en.Then;
import cucumber.api.java.en.When;
import org.fluentlenium.core.annotation.Page;

public class LogInSteps extends AbstractCucumberTest {

private final String BO_USERNAME = prop("operatorUserName");
private final String BO_PASSWORD = prop("operatorPassword");

@page
private LogInPage logInPage;

@page
private DashboardPage dashboardPage;

@before
public void before(Scenario scenario) {
super.setUpBefore(scenario);
}

@after
public void after(Scenario scenario) {
super.tearDownAfter(scenario);
}

@given("^the operator navigates to back office login page$")
public void the_operator_navigates_to_back_office_login_page() {
goTo(logInPage);
logInPage.isAt();
}

@given("^the operator navigates back to the back office login page$")
public void the_operator_navigated_back_to_the_back_office_login_page() {
goTo(logInPage);
}

@given("^the operator is logged in and on the dashboard$")
public void the_operator_is_logged_in_and_on_the_dashboard() {
goTo(logInPage);
logInPage.isAt();
logInPage.fillAndSubmitForm(BO_USERNAME, BO_PASSWORD);
logInPage.confirmSuccessfulLogIn();
}

@when("^the operator submits login page$")
public void the_operator_submits_login_page() {
logInPage.fillAndSubmitForm(BO_USERNAME, BO_PASSWORD);
}

@then("^the operator is successfully logged in$")
public void the_operator_is_successfully_logged_in() {
logInPage.confirmSuccessfulLogIn();
}

@then("^the operator is successfully logged out$")
public void theOperatorIsSuccessfullyLoggedOut() {
dashboardPage.logout();
logInPage.isAt();
}

@when("^the operator submits invalid login credentials$")
public void theOperatorSubmitsInvalidLoginCredentials() {
goTo(logInPage);
logInPage.isAt();
logInPage.fillAndSubmitForm(BO_USERNAME + "111", BO_PASSWORD);
}

@then("^the operator is not successfully logged in$")
public void theOperatorIsNotSuccessfullyLoggedIn() {
logInPage.confirmUnsuccessfulLogin();
}
}

`

[slawekradzyminski]

Can you try to extend FluentCucumberTest as stated in docs?
http://fluentlenium.org/docs/test-runners/#cucumber

[paulsjohnson91]

Hi The AbstractCucumberTest class extends the FluentCucumberTest class.

Thanks,

[koryl]

Hi @paulsjohnson91, I was trying reproduce mentioned by you issue and I found out that it is not related with Java 11 because it worked for me smoothly.

Please, make sure that your runner class uses
@RunWith(FluentCucumber.class)
instead of
@RunWith(Cucumber.class)
When using Cucumber.class as runner I've noticed the problem and message you have mentioned (but not always which is confusing). When using FluentCucumber.class it worked well.

Let us know if it resolves your issue.

[paulsjohnson91]

Hi, For the scenario listed above I was not running with a runner I was running directly from the IDE. When we use runners we are using AbstractTestNGCucumberTests not JUnit. This setup was working before with Java8 using both the IDE and the TestNG runner to execute the tests.

[koryl]

Ok, now I understand. There were made few changes to handle integration with Cucumber which are related to you problem. More detail what was changed you can find here #612 and here http://fluentlenium.com/docs/test-runners/#cucumber
I will try to fix this in way to use FluentCucumberTest without any runner and to prevent to adding before and after hooks for all classes (for clarity and better performance).

The quickest way to fix this issue is add this class to your project and extend your AbstractCucumberClass with it:

    import org.fluentlenium.adapter.FluentTestRunnerAdapter;
    import org.fluentlenium.adapter.cucumber.FluentCucumberSharedMutator;

    public class FluentCucumberTest extends FluentTestRunnerAdapter {

        public FluentCucumberTest() {
            super(new FluentCucumberSharedMutator());
        }

        public void before(Scenario scenario) {
            starting(scenario.getName());
        }

        public void after(Scenario scenario) {
            if (scenario.isFailed()) {
                failed(scenario.getName());
            }
            finished(scenario.getName());
        }
    }

This issue will be updated when I found better way for injecting FluentLenium components without necessity for repeating before and after hooks.

[koryl]

I've merged bugfix to develop and it will be incorporated into next version.
@paulsjohnson91, this fix will resolve problem with creating instances of Pages but not with elements annotates with FindBy. If this is still an issue please try earlier mentioned FluentCucumber runner or create elements with use FluentWebElement element = el("#locator") instead.

[paulsjohnson91]

Great thanks, the page issue was fixed by this as long as I added the following to my test step classes:
@Before public void before(Scenario scenario){ super.before(scenario); }

I'm not currently having issues with elements which are initialised with @findby so everything seems to be working as expected now.

Thanks for the help