root
/
spring-framework
mirror of https://github.com/spring-projects/spring-framework.git
1
0
Fork 0
Code Issues Actions 8 Packages Projects Releases Wiki Activity
spring-framework/spring-test/spring-test.gradle

115 lines
4.9 KiB
Groovy
Raw Permalink Normal View History

Consistently use double quotes (even if no interpolation needed) Includes upgrade to Hibernate ORM 5.3.5, EclipseLink 2.7.3, Selenium HtmlUnit Driver 2.32.1, Jetty 9.4.12 RC2.
2018-08-16 21:32:44 +08:00
description = "Spring TestContext Framework"
Move modules to independent build files The main `build.gradle` file contains now only the common build infrastructure; all module-specific build configurations have been moved to their own build file. Issue: SPR-15885
2017-08-21 20:41:55 +08:00
Revert "Revert "Refactor Gradle tasks in Spring Framework build"" This reverts commit fb0d618751a073c067c41266b9601094ccaa7560.
2019-08-21 02:26:43 +08:00
apply plugin: "kotlin"
Move modules to independent build files The main `build.gradle` file contains now only the common build infrastructure; all module-specific build configurations have been moved to their own build file. Issue: SPR-15885
2017-08-21 20:41:55 +08:00
dependencies {
Upgrade to Gradle 7.2 This commit upgrades Gradle to 7.2. Gradle configuration names are updated accordingly. This also upgrades Gradle build plugins. See gh-26870
2021-05-22 03:16:30 +08:00
api(project(":spring-core"))
Consistently use double quotes (even if no interpolation needed) Includes upgrade to Hibernate ORM 5.3.5, EclipseLink 2.7.3, Selenium HtmlUnit Driver 2.32.1, Jetty 9.4.12 RC2.
2018-08-16 21:32:44 +08:00
optional(project(":spring-aop"))
optional(project(":spring-beans"))
optional(project(":spring-context"))
optional(project(":spring-jdbc"))
optional(project(":spring-orm"))
optional(project(":spring-tx"))
optional(project(":spring-web"))
optional(project(":spring-webflux"))
optional(project(":spring-webmvc"))
optional(project(":spring-websocket"))
Polishing
2023-08-02 05:52:48 +08:00
optional("com.jayway.jsonpath:json-path")
optional("io.micrometer:context-propagation")
optional("io.micrometer:micrometer-observation")
optional("io.projectreactor:reactor-test")
Jakarta EE 9 migration Upgrades many dependency declarations; removes old EJB 2.x support and outdated Servlet-based integrations (Commons FileUpload, FreeMarker JSP support, Tiles). Closes gh-22093 Closes gh-25354 Closes gh-26185 Closes gh-27423 See gh-27424
2021-09-17 15:14:07 +08:00
optional("jakarta.activation:jakarta.activation-api")
optional("jakarta.el:jakarta.el-api")
optional("jakarta.inject:jakarta.inject-api")
optional("jakarta.servlet:jakarta.servlet-api")
optional("jakarta.servlet.jsp:jakarta.servlet.jsp-api")
optional("jakarta.servlet.jsp.jstl:jakarta.servlet.jsp.jstl-api")
optional("jakarta.websocket:jakarta.websocket-api")
Align with Servlet 6.0 and introduce support for Jakarta WebSocket 2.1 Includes corresponding build upgrade to Tomcat 10.1.1 and Undertow 2.3.0 (while retaining runtime compatibility with Tomcat 10.0 and Undertow 2.2) Closes gh-29435 Closes gh-29436
2022-11-06 23:08:30 +08:00
optional("jakarta.websocket:jakarta.websocket-client-api")
Consistent dependency declarations
2023-08-02 06:56:50 +08:00
optional("jakarta.xml.bind:jakarta.xml.bind-api")
Revise support for JSR-330 and Jakarta @Inject for autowiring test constructors Closes gh-29851
2023-09-09 01:25:31 +08:00
optional("javax.inject:javax.inject")
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
optional("junit:junit")
Consistent dependency declarations
2023-08-02 06:56:50 +08:00
optional("org.apache.groovy:groovy")
optional("org.apache.tomcat.embed:tomcat-embed-core")
optional("org.aspectj:aspectjweaver")
Add support for JSON assertions using JSON compare This commit moves JSON content AssertJ support from Spring Boot. See gh-21178 Co-authored-by: Brian Clozel <brian.clozel@broadcom.com>
2024-03-15 20:14:38 +08:00
optional("org.assertj:assertj-core")
Consistent dependency declarations
2023-08-02 06:56:50 +08:00
optional("org.hamcrest:hamcrest")
Upgrade to HtmUnit 3.11.0 This commit upgrades to a major new release of HtmlUnit. This is a breaking change as HtmlUnit 3 moves to a `org.htmlunit` package and calling code needs to be restructured. Our use of Selenium has been adapted accordingly, moving to Selenium 3, using the new org.seleniumhq.selenium:htmlunit3-driver integration. Closes gh-30392
2024-03-11 17:51:57 +08:00
optional("org.htmlunit:htmlunit") {
exclude group: "commons-logging", module: "commons-logging"
}
Consistent dependency declarations
2023-08-02 06:56:50 +08:00
optional("org.jetbrains.kotlin:kotlin-reflect")
optional("org.jetbrains.kotlin:kotlin-stdlib")
optional("org.jetbrains.kotlinx:kotlinx-coroutines-core")
optional("org.jetbrains.kotlinx:kotlinx-coroutines-reactor")
optional("org.junit.jupiter:junit-jupiter-api")
optional("org.junit.platform:junit-platform-launcher") // for AOT processing
Add support for bean overriding in tests This commit introduces two sets of annotations (`@TestBean` on one side and `MockitoBean`/`MockitoSpyBean` on the other side), as well as an extension mecanism based on the `@BeanOverride` meta-annotation. Extension implementors are expected to only provide an annotation, a BeanOverrideProcessor implementation and an OverrideMetadata subclass. Closes gh-29917.
2023-12-14 18:43:37 +08:00
optional("org.mockito:mockito-core")
Upgrade to HtmUnit 3.11.0 This commit upgrades to a major new release of HtmlUnit. This is a breaking change as HtmlUnit 3 moves to a `org.htmlunit` package and calling code needs to be restructured. Our use of Selenium has been adapted accordingly, moving to Selenium 3, using the new org.seleniumhq.selenium:htmlunit3-driver integration. Closes gh-30392
2024-03-11 17:51:57 +08:00
optional("org.seleniumhq.selenium:htmlunit3-driver") {
Exclude commons-logging dependency in spring-test
2023-06-09 17:37:08 +08:00
exclude group: "commons-logging", module: "commons-logging"
Avoid accidental dependency on older version of Byte Buddy This commit allows Mockito-based tests in spring-test to work again in Eclipse IDE. This problem was uncovered while fixing gh-27365
2021-09-07 17:32:28 +08:00
exclude group: "net.bytebuddy", module: "byte-buddy"
}
optional("org.seleniumhq.selenium:selenium-java") {
exclude group: "net.bytebuddy", module: "byte-buddy"
}
Use dependency management in Framework build Prior to this commit, the Spring Framework build would partially use the dependency management plugin to import and enforce BOMs. This commit applies the dependency management plugin to all Java projects and regroups all version management declaration in the root `build.gradle` file (versions and exclusions). Some versions are overridden in specific modules for backwards-compatibility reasons or extended support. This commit also adds the Gradle versions plugin that checks for dependency upgrades in artifact repositories and produces a report; you can use the following: ./gradlew dependencyUpdates
2019-08-27 03:13:12 +08:00
optional("org.skyscreamer:jsonassert")
Consistent dependency declarations
2023-08-02 06:56:50 +08:00
optional("org.testng:testng")
optional("org.xmlunit:xmlunit-matchers")
Upgrade to Gradle 7.2 This commit upgrades Gradle to 7.2. Gradle configuration names are updated accordingly. This also upgrades Gradle build plugins. See gh-26870
2021-05-22 03:16:30 +08:00
testImplementation(project(":spring-context-support"))
Consistent dependency declarations
2023-08-02 06:56:50 +08:00
testImplementation(project(":spring-core-test"))
Upgrade to Gradle 7.2 This commit upgrades Gradle to 7.2. Gradle configuration names are updated accordingly. This also upgrades Gradle build plugins. See gh-26870
2021-05-22 03:16:30 +08:00
testImplementation(project(":spring-oxm"))
testImplementation(testFixtures(project(":spring-beans")))
testImplementation(testFixtures(project(":spring-context")))
testImplementation(testFixtures(project(":spring-core")))
testImplementation(testFixtures(project(":spring-tx")))
testImplementation(testFixtures(project(":spring-web")))
Consistent dependency declarations
2023-08-02 06:56:50 +08:00
testImplementation("com.fasterxml.jackson.core:jackson-databind")
testImplementation("com.rometools:rome")
testImplementation("com.thoughtworks.xstream:xstream")
Polishing
2023-08-02 05:52:48 +08:00
testImplementation("de.bechte.junit:junit-hierarchicalcontextrunner")
Consistent dependency declarations
2023-08-02 06:56:50 +08:00
testImplementation("io.projectreactor.netty:reactor-netty-http")
Jakarta EE 9 migration Upgrades many dependency declarations; removes old EJB 2.x support and outdated Servlet-based integrations (Commons FileUpload, FreeMarker JSP support, Tiles). Closes gh-22093 Closes gh-25354 Closes gh-26185 Closes gh-27423 See gh-27424
2021-09-17 15:14:07 +08:00
testImplementation("jakarta.annotation:jakarta.annotation-api")
testImplementation("jakarta.ejb:jakarta.ejb-api")
testImplementation("jakarta.interceptor:jakarta.interceptor-api")
testImplementation("jakarta.mail:jakarta.mail-api")
Polishing
2023-08-02 05:52:48 +08:00
testImplementation("jakarta.validation:jakarta.validation-api")
testImplementation("javax.cache:cache-api")
Replace dependency management plugin with built-in platform support
2022-08-30 22:18:49 +08:00
testImplementation("org.apache.httpcomponents:httpclient") {
exclude group: "commons-logging", module: "commons-logging"
}
Add test support to record async events, with Junit5 caveat This commit modifies the way the `@RecordApplicationEvents` annotation works in tests, allowing for capture of events from threads other than the main test thread (async events) and for the assertion of captured event from a separate thread (e.g. when using `Awaitility`). This is done by switching the `ApplicationEventsHolder` to use an `InheritedThreadLocal`. There is a mutual exclusion between support of asynchronous events vs support of JUnit5 parallel tests with the `@TestInstance(PER_CLASS)` mode. As a result, we favor the former and now `SpringExtension` will invalidate a test class that is annotated (or meta-annotated, or enclosed-annotated) with `@RecordApplicationEvents` AND `@TestInstance(PER_CLASS)` AND `@Execution(CONCURRENT)`. See gh-29827 Closes gh-30020
2023-02-24 00:33:41 +08:00
testImplementation("org.awaitility:awaitility")
Introduce @⁠EasyMockBean bean override example This commit introduces example support for a custom @⁠EasyMockBean annotation that allows tests to use EasyMock as the mocking framework for bean overrides in a test's ApplicationContext. The point of this exercise is to ensure that it is possible for third parties to introduce bean override support for mocking frameworks other than Mockito, and that they can do so with the APIs currently in place. Closes gh-33562
2024-09-18 19:59:56 +08:00
testImplementation("org.easymock:easymock")
Consistent dependency declarations
2023-08-02 06:56:50 +08:00
testImplementation("org.hibernate:hibernate-core-jakarta")
testImplementation("org.hibernate:hibernate-validator")
testImplementation("org.hsqldb:hsqldb")
testImplementation("org.junit.platform:junit-platform-testkit")
testRuntimeOnly("com.sun.xml.bind:jaxb-core")
testRuntimeOnly("com.sun.xml.bind:jaxb-impl")
testRuntimeOnly("org.glassfish:jakarta.el")
testRuntimeOnly("org.junit.support:testng-engine")
Upgrade to Gradle 7.2 This commit upgrades Gradle to 7.2. Gradle configuration names are updated accordingly. This also upgrades Gradle build plugins. See gh-26870
2021-05-22 03:16:30 +08:00
testRuntimeOnly("org.junit.vintage:junit-vintage-engine") {
Upgrade to Hamcrest 2.1 Closes gh-23467
2019-08-18 00:44:47 +08:00
exclude group: "junit", module: "junit"
}
Support custom properties file formats in @TestPropertySource Spring Framework 4.3 introduced the `PropertySourceFactory` SPI for use with `@PropertySource` on `@Configuration` classes; however, prior to this commit there was no mechanism to support custom properties file formats in `@TestPropertySource` for integration tests. This commit introduces support for configuring a custom `PropertySourceFactory` via a new `factory` attribute in `@TestPropertySource` in order to support custom file formats such as JSON, YAML, etc. For example, if you create a YamlPropertySourceFactory, you can use it in integration tests as follows. @SpringJUnitConfig @TestPropertySource(locations = "/test.yaml", factory = YamlPropertySourceFactory.class) class MyTestClass { /* ... /* } If a custom factory is not specified, traditional `*.properties` and `*.xml` based `java.util.Properties` file formats are supported, which was the existing behavior. Closes gh-30981
2023-08-04 17:10:07 +08:00
testRuntimeOnly("org.yaml:snakeyaml")
Move modules to independent build files The main `build.gradle` file contains now only the common build infrastructure; all module-specific build configurations have been moved to their own build file. Issue: SPR-15885
2017-08-21 20:41:55 +08:00
}
Ensure projects can be imported into Eclipse IDE with JDK 17 Prior to this commit, the Spring Framework projects could not be imported into Eclipse IDE when using JDK 17 to build the projects. The primary obstacle is the fact that Eclipse enforces a strict "no split packages between the unnamed module and a system module" rule when building with a "modular JDK" (such as JDK 17). Resources: - https://bugs.eclipse.org/bugs/show_bug.cgi?id=536928 - https://bugs.openjdk.java.net/browse/JDK-8215739 - http://mail.openjdk.java.net/pipermail/jigsaw-dev/2018-December/014077.html - https://stackoverflow.com/questions/51094274/eclipse-cant-find-xml-related-classes-after-switching-build-path-to-jdk-10/53824670#53824670 Since the bug (JDK-8215739) has not been fixed in OpenJDK, the strict "no split packages" rule does not apply to the Java compiler used in Spring Framework's Gradle build or the compiler in IntelliJ IDEA. Hence, this issue only arrises when building the framework in Eclipse IDE. This commit addresses this issue in the following affected projects. - spring-oxm: removal of the dependency on XPP3 which publishes javax.xml.namespace.QName as part of the JAR. The QName type is also published by the java.xml JDK 17 system module. To make the tests pass, we have switched to using the DomDriver instead of the XppDriver in our XStream tests. - spring-test: HtmlUnit has a transitive dependency on xml-apis which publishes several packages also published by java.xml JDK 17 system module. Thus, we have explicitly excluded the transitive dependency on xml-apis for our `optional` configuration. See gh-27407
2021-09-22 22:22:27 +08:00
// Prevent xml-apis from being used so that the corresponding XML APIs from
// the JDK's `java.xml` module are used instead. This allows spring-test to
// build in Eclipse IDE which fails to compile if there is a split package
// between a JDK system module and the unnamed module (for JARs on the
// classpath).
configurations.optional {
exclude group: "xml-apis", module: "xml-apis"
}
Migrate to TestNG Engine for the JUnit Platform in spring-test Prior to this commit, we had configured separate test tasks for JUnit and TestNG. In addition, we configured a standard `test` task that depended on the `junit` and `testNG` tasks, and we had an additional `aggregateTestReports` task that aggregated the reports from the JUnit and TestNG test tasks. Thanks to the introduction of the "TestNG Engine for the JUnit Platform", this commit simplifies our Gradle build in the spring-test module by running JUnit 4, JUnit Jupiter, and TestNG tests on the JUnit Platform in a single Gradle `test` task. See gh-27406
2021-09-15 20:15:59 +08:00
test {
description = "Runs JUnit 4, JUnit Jupiter, and TestNG tests."
Ensure aggregateTestReports task is UP-TO-DATE Prior to this commit, the standard Gradle `test` task was configured to execute all JUnit tests and had a dependency on the `testNG` task. In addition, the `aggregateTestReports` task depended on the results of the `test` and `testNG` tasks as input. Consequently, a subsequent execution of the `aggregateTestReports` task would not be considered UP-TO-DATE since the JUnit and TestNG results were both written to the same "test" reports folder. This commit introduces a new `junit` test task that allows JUnit and TestNG test output to be completely independent. The standard `test` task now depends on `junit` and `testNG` but does not execute any tests itself, and the `aggregateTestReports` task now depends on the individual `junit` and `testNG` results instead of on the mixed `test` results. See also: eec183ef2840d0e3cc20af01f69cda1adea7383e
2019-07-21 23:21:24 +08:00
useJUnitPlatform {
Migrate to TestNG Engine for the JUnit Platform in spring-test Prior to this commit, we had configured separate test tasks for JUnit and TestNG. In addition, we configured a standard `test` task that depended on the `junit` and `testNG` tasks, and we had an additional `aggregateTestReports` task that aggregated the reports from the JUnit and TestNG test tasks. Thanks to the introduction of the "TestNG Engine for the JUnit Platform", this commit simplifies our Gradle build in the spring-test module by running JUnit 4, JUnit Jupiter, and TestNG tests on the JUnit Platform in a single Gradle `test` task. See gh-27406
2021-09-15 20:15:59 +08:00
includeEngines "junit-vintage", "junit-jupiter", "testng"
Ensure aggregateTestReports task is UP-TO-DATE Prior to this commit, the standard Gradle `test` task was configured to execute all JUnit tests and had a dependency on the `testNG` task. In addition, the `aggregateTestReports` task depended on the results of the `test` and `testNG` tasks as input. Consequently, a subsequent execution of the `aggregateTestReports` task would not be considered UP-TO-DATE since the JUnit and TestNG results were both written to the same "test" reports folder. This commit introduces a new `junit` test task that allows JUnit and TestNG test output to be completely independent. The standard `test` task now depends on `junit` and `testNG` but does not execute any tests itself, and the `aggregateTestReports` task now depends on the individual `junit` and `testNG` results instead of on the mixed `test` results. See also: eec183ef2840d0e3cc20af01f69cda1adea7383e
2019-07-21 23:21:24 +08:00
}
Revise TestConventions to retain existing JUnit Platform options This commit revises the implementation of TestConventions so that existing JUnit Platform options from a pre-configured `test` task are copied instead of overridden. Closes gh-34827
2025-04-25 19:38:18 +08:00
// `include` test filters and system properties are configured in
// org.springframework.build.TestConventions in buildSrc.
Exclude TestCase classes in spring-test build When not excluded, TestNG will pick up nested TestCase classes and run them. This commit therefore filters out `*TestCase` test classes from the build since these are not intended to be executed with the build. See gh-27406
2021-09-15 22:08:36 +08:00
filter.excludeTestsMatching("*TestCase")
Revise TestConventions to retain existing JUnit Platform options This commit revises the implementation of TestConventions so that existing JUnit Platform options from a pre-configured `test` task are copied instead of overridden. Closes gh-34827
2025-04-25 19:38:18 +08:00
// Optionally configure Java Util Logging for the JUnit Platform.
Ensure aggregateTestReports task is UP-TO-DATE Prior to this commit, the standard Gradle `test` task was configured to execute all JUnit tests and had a dependency on the `testNG` task. In addition, the `aggregateTestReports` task depended on the results of the `test` and `testNG` tasks as input. Consequently, a subsequent execution of the `aggregateTestReports` task would not be considered UP-TO-DATE since the JUnit and TestNG results were both written to the same "test" reports folder. This commit introduces a new `junit` test task that allows JUnit and TestNG test output to be completely independent. The standard `test` task now depends on `junit` and `testNG` but does not execute any tests itself, and the `aggregateTestReports` task now depends on the individual `junit` and `testNG` results instead of on the mixed `test` results. See also: eec183ef2840d0e3cc20af01f69cda1adea7383e
2019-07-21 23:21:24 +08:00
// systemProperty("java.util.logging.manager", "org.apache.logging.log4j.jul.LogManager")
}