Closed Invictum closed 6 years ago
Hello @Invictum
Please check if index.html in parent directory is correct and contains all tests?
Also, did you check it with latest jbehave - core - maven-plugin versions?
@YamStranger It correct, but there are no results here. All resources required for report (images, html, etc) located under modules target.
@Invictum thanks for your answer. Did you try it with latest version of jbehave, core, junit? Last version can be without this bug
@YamStranger Yes I rechecked it with latest version (core - 1.1.37-rc.6, jbehave - 1.13.0, serenity-maven-plugin - 1.1.37-rc.6) and got the same results. I have created test project for it at
git@github.com:Invictum/serenity-multi-module.git
@Invictum great, thanks!!
This can be done by placing a relative path to the parent target directory in the serenity.properties file in each module, e.g.
serenity.outputDirectory=../target/site/serenity
I am using Serenity BDD (1.1.34) with jBehave (1.12.0). For execution serenity-maven-plugin (1.1.34) is used. There is a multi-module maven project. It consists of several modules:
Each module contains full stack of related stuff required for test execution (including defenitions, steps, pages, etc.) Properties are different and defined in serenity.properties files on module level.
To run tests and make a report:
It work fine when this command is executed in module directory. But when I try to use in on parent POM level I got broken reports:
I assume for each module separate report should be generated?