How to use SliceBuilder class of net.serenitybdd.cucumber.suiteslicing package

The issue was traced to the browserTimeout parameter in the grid config.

You're defining your profiles in the wrong place. The correct place is directly under project:

<project>
    ...
    <profiles>

and then the plugin-configuration for that profile:

<project>
    ...
    <profiles>
    ...
      <build>
          <plugins>
             ....

That means you'll have to define the plugins mutliple times (per profile). The profile-information in configuration has to be removed.

Looks like you are indirectly running Serenity through the junit-vintage-engine. When executed this way, parallel execution is simply not supported.

To be exact you are running your tests through Surefire -> JUnit 5 -> JUnit Vintage -> JUnit 4 -> Serenity -> Cucumber.

You'd have to wait for JUnit Vintage to support parallel execution or get rid of JUnit 5 from your depencies so Surefire can run JUnit 4 directly.

However given that you are also using Spring you may not be able to get rid of JUnit 5.

You could ask Serenity to support JUnit 5 but I suspect they will be unable too. They have never bothered to contribute the extension points they'd need upstream. Instead they have hacked their stuff into Cucumber.

If you are using Cucumber you've got it almost right. I don't actually know what Serenity does.

The parameter type annotation should have a value that is a regular expression. This regular expression should match the values used in your step.

@ParameterType("[a-z0-9]+")
public String userName(String value){
    return value;
}

@ParameterType("[a-z0-9]+")
public String password(String value){
    return value;
}

Then in your step definition you can use the method names of the annotated methods as parameter types.

@When("I enter {userName} and {password}")
public void iAddUserNameAndPassword(String userName, String password) {
    user.addNewUserInfo(userName, password);
}

compile group: 'org.seleniumhq.selenium', name: 'selenium-chrome-driver', version: '3.0.1'

I'm not using Selenium. I'm using Gradle, Cucumber, Serenity.

If you are using Cucumber you've got it almost right. I don't actually know what Serenity does.

The parameter type annotation should have a value that is a regular expression. This regular expression should match the values used in your step.

@ParameterType("[a-z0-9]+")
public String userName(String value){
    return value;
}

@ParameterType("[a-z0-9]+")
public String password(String value){
    return value;
}

Then in your step definition you can use the method names of the annotated methods as parameter types.

@When("I enter {userName} and {password}")
public void iAddUserNameAndPassword(String userName, String password) {
    user.addNewUserInfo(userName, password);
}

If you are trying to run an After hook after each scenario tagged with "@tag1" in your example, you should mark the After hook with "@tag1". For more information on tagged hooks, please refer to the Cucumber documentation.

For you to test this page you need to be able to create the underlying object which has the id that makes up the dynamic part of your URL. In this case your trigger. You can retrieve the trigger and use its ID to make your URL.

So with Cucumber you might have something like

Given I have a trigger When I view the triggers add page ... And you could implement that with something like

Given 'I have a trigger' do
  @trigger = create_trigger
end

When 'I view the triggers add page' do
  visit trigger_add_page_path(trigger: @trigger)
end

Notice how the variable created in the Given is used in the When.

You'll have to work out your language/platform specifics that allow you to get this working, but hopefully this is enough to get you started.

The dependency is into the plugin in POM.xml:

<plugin>
            <groupId>net.serenity-bdd.maven.plugins</groupId>
            <artifactId>serenity-maven-plugin</artifactId>
            <version>${serenity.version}</version>
            <dependencies>
                <dependency>
                    <groupId>net.serenity-bdd</groupId>
                    <artifactId>serenity-core</artifactId>
                    <version>${serenity.version}</version>
                </dependency>
            </dependencies>

The dependencies should be between the rest of dependencies . . . .

Try to remove that dependency and past it into the dependencies, not in the plugin section.