You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on documentation and examples, it is unclear how in JUnit based scenario developers could add narrative documentation to be used in the reports.
After reading BDD in action and Serenity BDD documentation about the living documentation features, I had assumption and expectation that same features and functionalities would be available also when using just JUnit tests.
I tested this with current serenity-junit-starter, using Serenity BDD 3.6.12 and the template on Ubuntu Linux, openjdk 19.
I tried adding @Narrative annotation to the WhenSearchingForTerms test class.
I tried to add package-info.java to the starter.wikipedia package with @Narrative annotation.
Neither of those was processed into the content anywhere.
Additionally in the example case report while listing Automated Tests the link on Feature column item "When searching for terms" is to a non existent page.
Expectation:
Product documentation and or test cases would show and describe all the available features and capabilities that are available in different configurations.
Additional discussion:
I started to look at the source code of the product, but the codebase is huge and has layers of also old features - so it is not quite easy to understand how everything works.
I've tried to look around serenity-model, serenity-junit5 and serenity-core but it is hard to understand how things work together and where to actually start to read things. And build better understanding.
Any help and insight would be appreciated, and I could based on that contribute something to documentation and / or tests, so that other new people would not make the same mistakes.
Thanks for proposing to help Huima. Features like the @Narrative annotation are related to the JUnit 4 Serenity integration - the JUnit 5 integration is a completely different implementation, and doesn't have those features yet (it's still evolving feature-wise). @cliviu might have some ideas on this too.
Problem:
Based on documentation and examples, it is unclear how in JUnit based scenario developers could add narrative documentation to be used in the reports.
After reading BDD in action and Serenity BDD documentation about the living documentation features, I had assumption and expectation that same features and functionalities would be available also when using just JUnit tests.
I tested this with current serenity-junit-starter, using Serenity BDD 3.6.12 and the template on Ubuntu Linux, openjdk 19.
I tried adding @Narrative annotation to the WhenSearchingForTerms test class.
I tried to add package-info.java to the starter.wikipedia package with @Narrative annotation.
Neither of those was processed into the content anywhere.
Additionally in the example case report while listing Automated Tests the link on Feature column item "When searching for terms" is to a non existent page.
Expectation:
Product documentation and or test cases would show and describe all the available features and capabilities that are available in different configurations.
Additional discussion:
I started to look at the source code of the product, but the codebase is huge and has layers of also old features - so it is not quite easy to understand how everything works.
I've tried to look around serenity-model, serenity-junit5 and serenity-core but it is hard to understand how things work together and where to actually start to read things. And build better understanding.
Any help and insight would be appreciated, and I could based on that contribute something to documentation and / or tests, so that other new people would not make the same mistakes.
I already also asked in the discussion group:
https://matrix.to/#/!QxFcPAtRfsRjFzyfCj:gitter.im/$mdgCqmcO4AGKTU79acZBtrEFclr3B0JR4tcj0tvhz5w?via=gitter.im&via=matrix.org
The text was updated successfully, but these errors were encountered: