Skip to content

Commit 468382b

Browse files
Merge pull request #2642 from Nordix/siiri/hack-ci-readme-updates
📖 Update info on running e2e locally
2 parents e302d1e + 51e727a commit 468382b

File tree

1 file changed

+49
-0
lines changed

1 file changed

+49
-0
lines changed

test/e2e/README.md

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,55 @@ export GINKGO_FOCUS="upgrade"
3535
./hack/ci-e2e.sh
3636
```
3737

38+
`GINKGO_FOCUS` can be set manually to run specific tests. The options for these
39+
can be found as the first string value (formatting included) of the line with
40+
`Describe` or `It`. These can also be combined with other proceeding sections to
41+
match to even more specific test sections. The value `GINKGO_FOCUS` uses is a
42+
regexp that should match the description of the spec but not match the regexp
43+
specified in `GINKGO_SKIP`.
44+
45+
Example:
46+
47+
```go
48+
var _ = Describe("basic", ...
49+
It("should control power cycle of BMH though annotations", ...
50+
...
51+
)
52+
)
53+
```
54+
55+
Could be used with:
56+
57+
```bash
58+
export GINKGO_FOCUS="basic should control power"
59+
```
60+
61+
Additionally, if you wish to run multiple different tests, just maually
62+
add another `--focus=` with string to the root Makefile's `test-e2e`
63+
target.
64+
65+
Skipping tests works otherwise similiarly to adding focus, but in the Makefile
66+
`GINKGO_SKIP` is split separated by space. Thus, you can either use
67+
test-specific words with it or you can add another `--skip=` with a longer
68+
string to the `test-e2e` target.
69+
70+
`BMC_PROTOCOL` can also be set manually. By default the [ci-e2e.sh](https://github.com/metal3-io/baremetal-operator/blob/main/hack/ci-e2e.sh)
71+
script runs it as `redfish`, but it can also be set to `redfish-virtualmedia`,
72+
`redfish`, or `ipmi`. Ipmi uses `vbmc` as the BMO e2e emulator, whereas the
73+
others use `sushy-tools`.
74+
75+
After the tests are run, please ensure proper cleanup before running them again.
76+
The due process for ensuring all is clean for the next run is (in the
77+
root directory):
78+
79+
```bash
80+
./hack/clean-e2e.sh
81+
make clean
82+
sudo rm -rf ./test/e2e/images
83+
```
84+
85+
In addition, make sure related docker containers are removed as well.
86+
3887
It is also possible to run the tests with the fixture provider instead of
3988
Ironic. Without any changes, the whole suite (including optional tests) will be
4089
run. Please note, however, that it is quite questionable to call this

0 commit comments

Comments
 (0)