Closed donraab closed 4 years ago
Please assign this ticket to me @donraab
Thanks for volunteering @prathasirisha ! Once you commented here, you showed up in the assignee list so I assigned.
Requesting guidance on how to proceed with this issue @nikhilnanivadekar @donraab @motlin
Context- We have a total of 150k tests in unit-tests module in EC.
Questions-
Do we still want to enable mutation testing for the ~10k tests ?
Do we create separate builds for each of the sub folders like bag, bimap, set, etc. to reduce the number of tests running in a single build? Or any other grouping logic for that matter.
Do we identify top contenders that need this testing in place and only run the mutation tests for them?
Or if there are any other ideas from the group.
I can share the output of the pitest if anyone is interested from #1 run.
The out of memory error happens for how much JVM memory? Is there a way to bump that up? We can run this in TeamCity which gives us higher configuration build runners if that’ll help
I ran with 16gigs of RAM and it did not help.
With mutation testing, you get a lot of value from running the tests once. When you got them running, what did you find? Any failures?
On Sun, Apr 12, 2020 at 9:05 PM Nikhil Nanivadekar notifications@github.com wrote:
The out of memory error happens for how much JVM memory? Is there a way to bump that up? We can run this in TeamCity which gives us higher configuration build runners if that’ll help
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/eclipse/eclipse-collections/issues/807#issuecomment-612704330, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAB3UIULD3WWMQKEHDHXBM3RMJQL5ANCNFSM4K7IBZGA .
I think we should ask @prathasirisha to submit a PR and set up a GitHub Actions build for the configuration we got working so we can review the results. Make sense?
Yup that’ll be better for review and observation.
Sounds good. I will do as suggested by @donraab and we can review the results then.
Excellent, thank you @prathasirisha!
Please review them - @nikhilnanivadekar @motlin @donraab
We should have mutation tests running in the Eclipse Collections build so we can discover and address more edge cases in our tests.
Pitest