Skip to content

Commit d4a6cfe

Browse files
astefanuttiopenshift-merge-robot
authored andcommitted
test: Document how to run e2e tests locally
1 parent 922dd7a commit d4a6cfe

File tree

1 file changed

+31
-1
lines changed

1 file changed

+31
-1
lines changed

README.md

Lines changed: 31 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
# codeflare-operator
2+
23
Operator for installation and lifecycle management of CodeFlare distributed workload stack, starting with MCAD and InstaScale
34

45
<!-- Don't delete these comments, they are used to generate Compatibility Matrix table for release automation -->
@@ -14,7 +15,36 @@ CodeFlare Stack Compatibility Matrix
1415
| KubeRay | v0.5.0 |
1516
<!-- Compatibility Matrix end -->
1617

17-
## Release process
18+
## Development
19+
20+
### Testing
21+
22+
The e2e tests can be executed locally by running the following commands:
23+
24+
1. Setup the test cluster:
25+
26+
```bash
27+
# Create a KinD cluster
28+
$ kind create cluster --image kindest/node:v1.25.8
29+
# Install the CRDs
30+
$ make install
31+
```
32+
33+
2. Start the operator locally:
34+
35+
```bash
36+
$ make run
37+
```
38+
39+
3. In a separate terminal, run the e2e suite:
40+
41+
```bash
42+
$ make test-e2e
43+
```
44+
45+
Alternatively, You can run the e2e test(s) from your IDE / debugger.
46+
47+
## Release
1848

1949
Prerequisite:
2050
- Build and release [MCAD](https://github.com/project-codeflare/multi-cluster-app-dispatcher)

0 commit comments

Comments
 (0)