@bennetelli I tried to add a test for the test execution listener, but I am not sure I could add more assertions to verify the operation in the TogglzTestExecutionListener.

Codecov Report

Patch coverage has no change and project coverage change: +0.17 🎉

Comparison is base (6e19b44) 56.04% compared to head (86a7bdd) 56.21%.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@             Coverage Diff              @@
##             master    #1002      +/-   ##
============================================
+ Coverage     56.04%   56.21%   +0.17%     
- Complexity      921      924       +3     
============================================
  Files           178      178              
  Lines          4527     4527              
  Branches        597      597              
============================================
+ Hits           2537     2545       +8     
+ Misses         1832     1822      -10     
- Partials        158      160       +2     

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

Making it standalone is better.

Like the existing spring boot starters example, spring-boot-starter-web and spring-boot-starter-test, spring-boot-starter-security and spring-security-test...

None of the starters include a test module.

If adding it into the togglze-starter, it will affect the test running described as I have encountered in the issue comments, I have to exclude it again.

I think we need to find a better way to achieve this. With these changes, projects using togglz with Feature enum would not need to add the new spring-test dependency, but projects using the application.yml file to declare their feature toggles would need to do it.

IMO that should be hidden for the users and they should not have to add an additional dependency in this case.

We gave up using this module in projects. In the past years of using Spring Boot in projects, I never encountered a case like this, adding a module destroyed the project test contexts.