Open codeconsole opened 1 month ago
For the org.grails.spring.context.support.PluginAwareResourceBundleMessageSource related errors, StaticMessageSource is the expected MessageSource type for testing which provides an addMessage method. The bean is set as StaticMessageSource here:
messageSource(StaticMessageSource)
https://github.com/grails/grails-testing-support/pull/431 fixes 28 of the ~52 new failing tests.
I just removed GrailsAutoConfiguration
It was registering grailsApplicationPostProcessor
after the test grailsApplicationPostProcessor
so the TestRuntimeGrailsApplicationPostProcessor
was being ignored because it had the same name.
https://github.com/grails/grails-testing-support/pull/435
I am only seeing 9 failing tests? https://github.com/grails/grails-core/actions/runs/11079311377/job/30823450376
That made an massive difference. Down to 3 distinct test failures on https://github.com/grails/grails-core/pull/13702/files, these each get run 3 times on https://github.com/grails/grails-core/actions/runs/11079311377/job/30823450376
Full list of failing tests: https://github.com/grails/grails-core/pull/13702/files
There are parts of grails-core are not 100% working. These are identified by failing tests which need to be fixed.
DataBindingConfigurationSpec.groovy Ordering
RespondMethodSpec ContentFormatControllerTests CommandObjectNoDataSpec WithFormatContentTypeSpec GrailsWebDataBinderConfigurationSpec CommandObjectsSpec