Skip to content
New issue

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

JUnit 5 to support min performance testing if not the advanced peformance specification #3375

Closed
nagkumar opened this issue Jul 2, 2023 · 1 comment

Comments

@nagkumar
Copy link

nagkumar commented Jul 2, 2023

It is good if JUnit 5 support

@RepeatedTest(10) at class and more so at suite level and make sure this annotation is supported with tests parallel execution.

With that simple repeat execution support, unit tests can definitely expose concurrency issues much faster at development time itself.

additionally it can also support

rampup and number of threads to use simpler to JMeter testplan.

Goal here is not the latency measurements but to make sure concurrency is exposing any object state issues.

@marcphilipp marcphilipp changed the title JUnit 5 to support min peformance testing if not the advanced peformance specification JUnit 5 to support min performance testing if not the advanced peformance specification Jul 7, 2023
@marcphilipp
Copy link
Member

Team decision: Repeating tests and running them concurrently at the class/suite level does not necessarily surface concurrency issues. In our experience, it is best to write targeted tests that use multiple threads that exercise a particular use case that you suspect may have concurrency issues.

@marcphilipp marcphilipp closed this as not planned Won't fix, can't repro, duplicate, stale Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants