Contributing - Build prerequisites? (mvnw verify fails)

[Rudolf-AT]

Hi,
I assume something is missing on my build setup.
Currently I try to build serenity-core (4.2.16, main) using ./mvnw clean verify and there is a failing test which stops the "verify":

[ERROR]   WhenGeneratingRequirementsReportData.a requirement with a failing tests is a failure:133 Condition not satisfied:
outcomes.failingRequirementsCount == 1
|        |                        |
|        0                        false
RequirementsOutcomes{requirementOutcomes=[

I use a fresh installed Ubuntu 24.04 on a 4GB machine. Installed

• firefox
• google chrome
• phantomjs
• geckodriver
• chromedriver
• openjdk-17.0.2
• npm

and I ran npx @puppeteer/browsers install chrome@stable.

Any idea what could be missing?

[Rudolf-AT]

Some more details:

in "net.thucydides.core.requirements.WhenGeneratingRequirementsReportData", the following tests fail:

- "should report test results associated with specified requirements"
- "a requirement with a failing tests is a failure"
- "should get test outcomes for a given release"
- "should get all nested test outcomes for a given release"

Workaround: Skip to build: comment out these four tests.

In "net.serenitybdd.plugins.jira.client.WhenIdentifyingCustomFields", tests fail - obviously since there is no Jira available during my build.

Workaround: Skip to build: comment out the Jira modules:

<!--module>serenity-jira-plugin</module-->
<!--module>serenity-jira-requirements-provider</module-->

Additionally, I set the following environment variables:

export JIRA_USERNAME=
export JIRA_API_TOKEN=
export JIRA_WEBSERVICE_URL=
export BROWSERSTACK_KEY=
export BROWSERSTACK_USER=
export SAUCE_USERNAME=
export SAUCE_ACCESS_KEY=
export LT_USERNAME=
export LT_ACCESS_KEY=

Of course these workarounds may leave some gaps in the build (like no Jira plugin).