diff --git a/Release-process-for-v5.md b/Release-process-for-v5.md
index 07b673c..0f19fa8 100644
--- a/Release-process-for-v5.md
+++ b/Release-process-for-v5.md
@@ -34,6 +34,22 @@
 
 Check uploaded jars in http://repo.spring.io/libs-milestone-local/org/springframework/batch and do a smoke test with the deployed milestone version: check the integrity of the artifacts to see if jars are not corrupted or empty, etc.
 
+#### Test within an IDE
+
+* Download the [release test project](https://raw.githubusercontent.com/wiki/spring-projects/spring-batch/projects/spring-batch-release-test.zip) and unzip it
+* Open it in your IDE and update the release version to test + comment the spring-staging repository
+* Run the `MyBatchJobConfiguration` class and then the `MyBatchJobTests` suite
+
+#### Test on the CLI
+
+```
+$>wget https://raw.githubusercontent.com/wiki/spring-projects/spring-batch/projects/spring-batch-release-test.zip
+$>unzip spring-batch-release-test.zip && cd spring-batch-release-test
+$>vim pom.xml # update the release version to test and comment the spring-staging repository
+$>mvn exec:java -Dexec.mainClass=MyBatchJobConfiguration # make sure the job is executed correctly
+$>mvn test # make sure the tests pass (no functional tests here, we are only checking the integrity of `spring-batch-test.jar`)
+```
+
 ❗ Heads-up: The "Artifactory Milestone Release" workflow is designed to be idempotent (it has no git side effects). If something is wrong with the milestone release, the same workflow can be re-run with the same version and a new milestone will override the corrupted one on the milestone repository. ❗ 
 
 ## Part 2.2: Release GAs to Maven Central
@@ -47,6 +63,22 @@ Check uploaded jars in http://repo.spring.io/libs-milestone-local/org/springfram
 
 Check uploaded jars in http://repo.spring.io/libs-staging-local/org/springframework/batch and do a smoke test with the staged release: check the integrity of the artifacts to see if jars are not corrupted or empty, etc.
 
+##### Test within an IDE
+
+* Download the [release test project](https://raw.githubusercontent.com/wiki/spring-projects/spring-batch/projects/spring-batch-release-test.zip) and unzip it
+* Open it in your IDE and update the release version to test + comment the spring-milestones repository
+* Run the `MyBatchJobConfiguration` class and then the `MyBatchJobTests` suite
+
+#### Test on the CLI
+
+```
+$>wget https://raw.githubusercontent.com/wiki/spring-projects/spring-batch/projects/spring-batch-release-test.zip
+$>unzip spring-batch-release-test.zip && cd spring-batch-release-test
+$>vim pom.xml # update the release version to test and comment the spring-milestones repository
+$>mvn exec:java -Dexec.mainClass=MyBatchJobConfiguration # make sure the job is executed correctly
+$>mvn test # make sure the tests pass (no functional tests here, we are only checking the integrity of `spring-batch-test.jar`)
+```
+
 ❗ Heads-up: The "Artifactory Staging" workflow is designed to be idempotent (it has no git side effects). If something is wrong with staged artifacts, the workflow "Artifactory Staging" can be re-run with the same version and a new release will override the corrupted one on the staging repository. ❗
 
 ### Part 2.2.3: Promote the release to Maven Central