spring-boot/spring-boot-project/spring-boot-cli/test-samples/integration_auto.groovy

package com.example

@SpringBootApplication
@SpringBootTest(classes=RestTests, webEnvironment=WebEnvironment.RANDOM_PORT)
class RestTests {

	@Autowired
	TestRestTemplate testRestTemplate;

	@Test
	void testHome() {
		assertEquals('Hello', testRestTemplate.getForObject('/', String))
	}

	@RestController
	static class Application {
		@RequestMapping('/')
		String hello() { 'Hello' }
	}

}
Fix TestCommandIntegrationTests after removal of deprecated test support See gh-6971 See gh-6973 8 years ago			`package com.example`

			`@SpringBootApplication`
			`@SpringBootTest(classes=RestTests, webEnvironment=WebEnvironment.RANDOM_PORT)`
Ensure CLI adds @EnableAutoConfiguration in an appropriate place Up to now we have been treating the first class to be compiled as the "main" application and adding @EnableAutoConfiguration. This isn't always appropriate (e.g. if it's a test case), so now we look for an appropriate annotation before falling back to the old behaviour. In addition ensures classes with a field of type Reactor trigger the reactor auto imports. See gh-969 11 years ago			`class RestTests {`

Fix TestCommandIntegrationTests after removal of deprecated test support See gh-6971 See gh-6973 8 years ago			`@Autowired`
			`TestRestTemplate testRestTemplate;`
Ensure CLI adds @EnableAutoConfiguration in an appropriate place Up to now we have been treating the first class to be compiled as the "main" application and adding @EnableAutoConfiguration. This isn't always appropriate (e.g. if it's a test case), so now we look for an appropriate annotation before falling back to the old behaviour. In addition ensures classes with a field of type Reactor trigger the reactor auto imports. See gh-969 11 years ago
			`@Test`
			`void testHome() {`
Fix TestCommandIntegrationTests after removal of deprecated test support See gh-6971 See gh-6973 8 years ago			`assertEquals('Hello', testRestTemplate.getForObject('/', String))`
Ensure CLI adds @EnableAutoConfiguration in an appropriate place Up to now we have been treating the first class to be compiled as the "main" application and adding @EnableAutoConfiguration. This isn't always appropriate (e.g. if it's a test case), so now we look for an appropriate annotation before falling back to the old behaviour. In addition ensures classes with a field of type Reactor trigger the reactor auto imports. See gh-969 11 years ago			`}`

			`@RestController`
			`static class Application {`
			`@RequestMapping('/')`
			`String hello() { 'Hello' }`
			`}`
Fix TestCommandIntegrationTests after removal of deprecated test support See gh-6971 See gh-6973 8 years ago
Ensure CLI adds @EnableAutoConfiguration in an appropriate place Up to now we have been treating the first class to be compiled as the "main" application and adding @EnableAutoConfiguration. This isn't always appropriate (e.g. if it's a test case), so now we look for an appropriate annotation before falling back to the old behaviour. In addition ensures classes with a field of type Reactor trigger the reactor auto imports. See gh-969 11 years ago			`}`