You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: core-codemods/src/test/java/io/codemodder/codemods/integration/README.md
+26-4Lines changed: 26 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,23 +8,45 @@ This is a test framework, built to test that each codemod does not break the fun
8
8
- A main Dockerfile will be used to generate two containers, the generated images will use a specific test project image as base and the codemod will be run in just one of them. Finally, we will have two containers running the same application but one of them will have undergone a code transformation.
9
9
- A request to an endpoint in the test application will be performed to verify the functionality has not changed.
10
10
11
-
### Running test locally
11
+
### How the framework works during CI/CD
12
+
- Codemodder base image is built at the pipeline context with the last changes in a PR.
13
+
- Test projects images are built at the pipeline context with the last changes in a PR.
14
+
- Integration tests are executed using the latest generated images.
15
+
- Generated images only live during the pipeline execution, a new commit wil generate new images.
16
+
17
+
### Running an integration test locally
18
+
All what you need to do is running the integration test, required images will be pulled from the public
Run the `docker build`command in the `codemodder-java` root directory, the `CODEMOD_ID` argument must have the value of the ID of the codemod we want to test
21
43
and the `CODEMODDER_BASE_IMAGE` argument should have the name of the codemodder base image we want to use as name.
0 commit comments