We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi Guys,
I faced the issue after migrating my test project to jUnit5. if I run some test class with Parametrised tests directly then the report look correct:
but if I run this test class from a tests suite like: @suite @SelectClasses({ MyTestClass.class })
public class MyTestSuite { } the report looks :
my build: 'net.serenity-bdd:serenity-core:3.3.2' 'net.serenity-bdd:serenity-junit5:3.3.2' 'org.junit.platform:junit-platform-suite-engine:1.9.0'
and SerenityJUnit5Extension on class level
Do you have any thoughts on this?
The text was updated successfully, but these errors were encountered:
Hmmm, I haven't used the JUnit 5 @suite and @selectClass annotations - I imagine they aren't supported yet - @cliviu?
Sorry, something went wrong.
@wakaleo In Junit5 docs said that they migrated from @RunWith(JUnitPlatform.class) to the @suite
I'm also not sure right now, I have to take a look. Most probably is not supported yet.
@cliviu It would be great to add support to these annotations to the next Serenity version, if possible of course ))
No branches or pull requests
Hi Guys,
I faced the issue after migrating my test project to jUnit5.
if I run some test class with Parametrised tests directly then the report look correct:
but if I run this test class from a tests suite like:
@suite
@SelectClasses({
MyTestClass.class
})
public class MyTestSuite {
}
the report looks :
my build:
'net.serenity-bdd:serenity-core:3.3.2'
'net.serenity-bdd:serenity-junit5:3.3.2'
'org.junit.platform:junit-platform-suite-engine:1.9.0'
and SerenityJUnit5Extension on class level
Do you have any thoughts on this?
The text was updated successfully, but these errors were encountered: