@ApplicationModuleTest in separate test files does not cache the ApplicationContext

[stephen-j-arnold]

Somewhat related to #725

When creating @ApplicationModuleTest's across test files within the same module, the ApplicationContext is not cached. From what I can see, ModuleContextCustomizerFactory.hashCode() is considering the source Class (which is the Test class) and that results in separate tests to be considered 'different' from a AC cache perspective. Though, from an actual AC perspective, these are the same contexts.

Relatively easy to re-produce in the spring-modulith-example-full module. I just added a duplicate OrderIntegrationTest called AnotherOrderIntegrationTest in a separate test file, and when running these together, I'd expect to have 1 AC but am seeing 2. Along with 2 cache misses logging.level.org.springframework.test.context.cache=debug, where I'd expect 1 (loading it for the first test (miss) but not the second (hit)).

[odrotbohm]

This has been tweaked to rather resort to the underlying execution than the individual test class. Feel free to give the 1.4 or 1.3.3 snapshots a try.

[stephen-j-arnold]

Sorry - I'm just getting to pull in 1.3.4 now & can confirm this issue is still present. Seems to be coming from ModuleTypeExcludeFilter now. Can we make the same tweak to the equals and hashCode functions on that object? From what I can see, that does seem to resolve the issue fully. Thank you!