Skip to content

Make core auto-configuration tests more independent #44513

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.

Sign up for GitHub

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

Jump to bottom
Closed
wilkinsona opened this issue Mar 3, 2025 · 0 comments
Closed

Make core auto-configuration tests more independent #44513

wilkinsona opened this issue Mar 3, 2025 · 0 comments
Assignees
@wilkinsona
Labels
type: task A general task
Milestone
3.3.10

Comments

@wilkinsona
Copy link
Member

The following all reference auto-configuration classes for specific technologies:

  • AutoConfigurationImportSelectorTests
  • ConditionEvaluationReportTests
  • ImportAutoConfigurationImportSelectorTests

Rework them to reduce unnecessary coupling of auto-configuration packages.
@wilkinsona wilkinsona added the type: task A general task label Mar 3, 2025
@wilkinsona wilkinsona added this to the 3.3.x milestone Mar 3, 2025
@wilkinsona wilkinsona self-assigned this Mar 3, 2025
This was referenced Mar 5, 2025
Closed
Closed
@wilkinsona wilkinsona modified the milestones: 3.3.x, 3.3.10 Mar 5, 2025
wilkinsona added a commit that referenced this issue Mar 5, 2025
@wilkinsona
Increase independence of core auto-configuration tests
8e49a4e 
Remove some more references to Thymeleaf and FreeMarker
auto-configuration that were missed in 85ffbbc.

See gh-44513
wilkinsona added a commit that referenced this issue Mar 6, 2025
@wilkinsona
Further improve independence of core auto-configuration tests
c849caf 
See gh-44513
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wilkinsona wilkinsona

Labels
type: task A general task
Projects
None yet
Milestone
3.3.10
Development

No branches or pull requests
1 participant
@wilkinsona