phosphor-host-ipmid/docs/testing.md

26 it all to go, and clone the CI scripts:
29 mkdir openbmc-ci-tests
30 cd openbmc-ci-tests
46 `run-unit-test-docker.sh`, you can't run the CI with untracked changes anyways,
55 git worktree add /path/to/openbmc-ci-tests/phosphor-host-ipmid
58 Now, if you `cd /path/to/openbmc-ci-tests`, you should see a directory
66 up `/path/to/openbmc-ci-tests/openbmc-build-scripts/run-unit-test-docker.sh` and
94 cd openbmc-ci-tests
99 git remote add /path/to/openbmc-ci-tests/phosphor-host-ipmid ci
100 git push ci
103 This method would require you to push your topic branch to `ci` and then
109 git push ci
110 cd /path/to/openbmc-ci-tests/phosphor-host-ipmid
114 You can also create a symlink from your Git workspace into `openbmc-ci-tests/`.
116 in parallel while the tests run, and since the CI scripts are unhappy when you
121 The OpenBMC CI scripts take care of the build for you, and run the test suite.
135 `openbmc-ci-tests/phosphor-host-ipmid/test/test-suite.log`, as well as being
351 `sensorhandler-tests` branch in your CI worktree, which will involve releasing
359 cd /path/to/openbmc-ci-tests/phosphor-host-ipmid
453 cd openbmc-ci-tests/phosphor-host-ipmid
458 This won't disturb the rest of your Git repo state, and will put your CI