src-spring-framework/spring-core-test/spring-core-test.gradle

description = "Spring Core Test"

dependencies {
	api(project(":spring-core"))
	api("org.junit.jupiter:junit-jupiter-api")
	api("org.assertj:assertj-core")
	compileOnly("org.junit.jupiter:junit-jupiter")
	compileOnly("org.junit.platform:junit-platform-engine")
	compileOnly("org.junit.platform:junit-platform-launcher")
	implementation("com.thoughtworks.qdox:qdox")
}

jar {
	manifest {
		attributes(
				'Premain-Class': 'org.springframework.aot.agent.RuntimeHintsAgent',
				'Can-Redefine-Classes': 'true'
		)
	}
}
Add module to support testing of generated code Add a new unpublished `spring-core-test` module to support testing of generated code. The module include a `TestCompiler` class which can be used to dynamically compile generated Java code. It also include an AssertJ friendly `SourceFile` class which uses qdox to provide targeted assertions on specific parts of a generated source file. See gh-28120 3 years ago			`description = "Spring Core Test"`

			`dependencies {`
			`api(project(":spring-core"))`
Add RuntimeHintsAgent Java agent With the introduction of `RuntimeHints`, we can now contribute reflection, resources and proxies hints that describe the expected runtime behavior of the application. While this can be verified at runtime with smoke tests, managing such tests and compiling to native there is not very efficient. This commit introduces the new `RuntimeHintsAgent`, a Java agent that instruments JDK methods related to `RuntimeHints`. It is different from the GraalVM agent, which aims at collecting all the required hints for the runtime behavior of an application and dump those in the expected format. Here, the `RuntimeHintsAgent` can collect the related invocations only for a delimited scope (typically, a lambda within a test) and later check those against a `RuntimeHints` instance. In the case of testing `RuntimeHintsRegistrar` implementations, the process is reversed: instead of manually checking for registered hints in a `RuntimeHints` instance, tests should exercise the use cases and then check that the recorded behavior is in line with the prepared hints. This first commit adds the agent infrastructure that collects the invocations for all relevant JDK methods. See gh-27981 2 years ago			`api("org.junit.jupiter:junit-jupiter-api")`
Add module to support testing of generated code Add a new unpublished `spring-core-test` module to support testing of generated code. The module include a `TestCompiler` class which can be used to dynamically compile generated Java code. It also include an AssertJ friendly `SourceFile` class which uses qdox to provide targeted assertions on specific parts of a generated source file. See gh-28120 3 years ago			`api("org.assertj:assertj-core")`
Improve TestCompiler and allow lookup based class defines Update the `TestCompiler` so that classes can be defined using a `Lookup`. This update allows package-private classes to be accessed without needing a quite so unusual classloader setup. The `@CompileWithTargetClassAccess` should be added to any test that needs to use `Lookup` based defines. The test will run with a completed forked classloader so not to pollute the main classloader. This commit also adds some useful additional APIs. See gh-28120 3 years ago			`compileOnly("org.junit.jupiter:junit-jupiter")`
			`compileOnly("org.junit.platform:junit-platform-engine")`
			`compileOnly("org.junit.platform:junit-platform-launcher")`
Make QDox an implementation detail of spring-core-test Previously, com.thoughtworks.qdox:qdox was declared as an api dependency of spring-core-test despite it only being used in the module's internals. This resulted in it unnecessarily appearing on the compile classpath of consuming projects. This commit moves qdox to be an implementation dependency, removing it from the compile classpath of consuming projects but ensuring that it's still available at runtime. Closes gh-29066 2 years ago			`implementation("com.thoughtworks.qdox:qdox")`
Add module to support testing of generated code Add a new unpublished `spring-core-test` module to support testing of generated code. The module include a `TestCompiler` class which can be used to dynamically compile generated Java code. It also include an AssertJ friendly `SourceFile` class which uses qdox to provide targeted assertions on specific parts of a generated source file. See gh-28120 3 years ago			`}`
Add RuntimeHintsAgent Java agent With the introduction of `RuntimeHints`, we can now contribute reflection, resources and proxies hints that describe the expected runtime behavior of the application. While this can be verified at runtime with smoke tests, managing such tests and compiling to native there is not very efficient. This commit introduces the new `RuntimeHintsAgent`, a Java agent that instruments JDK methods related to `RuntimeHints`. It is different from the GraalVM agent, which aims at collecting all the required hints for the runtime behavior of an application and dump those in the expected format. Here, the `RuntimeHintsAgent` can collect the related invocations only for a delimited scope (typically, a lambda within a test) and later check those against a `RuntimeHints` instance. In the case of testing `RuntimeHintsRegistrar` implementations, the process is reversed: instead of manually checking for registered hints in a `RuntimeHints` instance, tests should exercise the use cases and then check that the recorded behavior is in line with the prepared hints. This first commit adds the agent infrastructure that collects the invocations for all relevant JDK methods. See gh-27981 2 years ago
			`jar {`
			`manifest {`
			`attributes(`
			`'Premain-Class': 'org.springframework.aot.agent.RuntimeHintsAgent',`
			`'Can-Redefine-Classes': 'true'`
			`)`
			`}`
			`}`