Spring/spring-boot
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Rename samples to smoke tests

Browse Source 
Closes gh-17197
This commit is contained in:
Madhura Bhave
2019-06-25 10:11:56 -07:00
parent 0b720b99b2
commit d5c0009c6e
743 changed files with 1440 additions and 2134 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
CONTRIBUTING.adoc
View File

@@ -125,7 +125,7 @@ find the process a little slower than the standard build.
[TIP]
====
If you want to run a build without the samples and integration tests, building the
If you want to run a build without the smoke tests and integration tests, building the
`spring-boot-project` module is enough. You can cd there and run the same command, or you
can run this from the top-level directory:
@@ -196,7 +196,7 @@ changes just won't be automatically formatted.
With the requisite eclipse plugins installed you can select
`import existing maven projects` from the `file` menu to import the code. You will
need to import the root `spring-boot` pom and the `spring-boot-samples` pom separately.
need to import the root `spring-boot` pom and the `spring-boot-smoke-tests` pom separately.
@@ -241,11 +241,11 @@ Maven is well supported by most Java IDEs. Refer to your vendor documentation.
== Integration Tests
The sample applications are used as integration tests during the build (when you
`./mvnw install`). Due to the fact that they make use of the `spring-boot-maven-plugin`
The smoke tests run as part of the build when you `./mvnw install`.
Due to the fact that they make use of the `spring-boot-maven-plugin`
they cannot be called directly, and so instead are launched via the
`maven-invoker-plugin`. If you encounter build failures running the integration tests,
check the `build.log` file in the appropriate sample directory.
check the `build.log` file in the appropriate smoke test directory.
== Cloning the git repository on Windows