This should allow us to ramp-up on the internals of the project and send a signal that the project is not dead.
Then there are some axis around which we would like to improve the project:
Easier adoption on large workspaces with legacy projects containing slow tests
More powerful filtering of filters
Inclusion filters
Filtering based on junit categories…
Auto-exclude slow tests?
Allow disabling infinitest completely for some project
To allow disabling file change monitoring and static analyazis
Improve user experience
(eclipse) Configurable error levels
(eclipse) Use dedicated marker instead of error marker
Investigate reporting errors inside the IDE test runner view?
Investigate using standard IDE preference pages to configure exclusions
Easier way to kill/suspend/restart running tests
Investigate possible integration and reporting with other testing tools
Code coverage integration (jacoco)
Mutation testing (PIT test)
Support of other test frameworks:
JUnit 5
Others?
Investigate "Integration"/UI tests enablement
allow to launch JUnit plug-in tests
allow to launch UI tests in a separate X server
Yep, it would be great!
--
You received this message because you are subscribed to the Google Groups "infinitest-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to infinitest-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--