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

Number of iterations of chained suites not used. #81

Open
lucasperin opened this issue Feb 2, 2022 · 1 comment · May be fixed by #85
Open

Number of iterations of chained suites not used. #81

lucasperin opened this issue Feb 2, 2022 · 1 comment · May be fixed by #85

Comments

@lucasperin
Copy link

Hey there, nice project! I have been using it a bunch, in particular the suites of suites feature.

One use case for me is having a suite dedicated for benchmark tests with high number of iterations. I use the main suite for unit tests with 1 iteration and the second (chained) suite for benchmarks with 10000 iterations. It seems that the number of iterations of the main suite overrides the others, so all my tests run 1 time only. Is this by design?

As a workaround, I am using MUNIT_TEST_OPTION_SINGLE_ITERATION in my unit test functions and setting the main suite to run 1000 iterations. This solves the problem apparently, however, all other suites will also run 10000 times if not using the single iteration option. I think it would be more flexible to get the number of iterations from each test suite, no?

@lucasperin
Copy link
Author

I have pushed a PR #85 with a modification to fix this behavior and another feature mentioned in #83

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant