Skip to content
This repository was archived by the owner on Feb 18, 2025. It is now read-only.

Commit e65781b

Browse files
authored
editing pass on test/README.md (#72)
1 parent 696fb51 commit e65781b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

test/README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ available (eg `nvida.com/gpu`).
88
The [../hack/](../hack) directory contains scripts that can be used to
99
create an appropriately configured test cluster using `kind` and to run
1010
the tests. The tests can be run in two primary modes:
11-
1. ***Fully automated*** The script [../hack/run-e2e.sh](../hack/run-e2e-sh)
11+
1. ***Fully automated*** The script [../hack/run-e2e-kind.sh](../hack/run-e2e-kind.sh)
1212
fully automates creating a properly configured `kind` cluster, deploying
1313
MCAD on the cluster, running all tests on the cluster, and then
1414
deleting the cluster when the tests are completed. For easy of use,
@@ -17,6 +17,6 @@ the tests. The tests can be run in two primary modes:
1717
2. ***Development mode*** The script [../hack/create-test-cluster.sh](../hack/create-test-cluster.sh)
1818
can be used to create a correctly configured test cluster without MCAD.
1919
You can then use either `make install; make run` or `make install; make kind-push; make deploy` to deploy MCAD onto the cluster.
20-
You can then either run test cases individually or use the script
20+
After MCAD is deployed on the cluster, you can then either run test cases individually or use the script
2121
[../hack/run-tests-on-cluster.sh](../hack/run-tests-on-cluster.sh) to
22-
run the entire test suite against your manually deployed MCAD.
22+
run the entire test suite against the MCAD you just deployed.

0 commit comments

Comments
 (0)