Interactive Shell

You can use cijoe interactively via the cijoe shell. When running the command:

cijoe

Invoking the above command starts a Bash subprocess/Shell with all the cijoe modules loaded. You can use Bash-completion to see what is available and play around.

Introspection

and inspect the default environment used by cijoe while in the Shell run:

printenv | grep CIJ_

Which will yield outout similar to:

CIJ_MODULES=/home/safl/.local/share/cijoe/modules
CIJ_TESTFILES=/home/safl/.local/share/cijoe/testfiles
CIJ_ENVS=/home/safl/.local/share/cijoe/envs
CIJ_TESTPLANS=/home/safl/.local/share/cijoe/testplans
CIJ_TEMPLATES=/home/safl/.local/share/cijoe/templates
CIJ_ECHO_TIME_STAMP=1
CIJ_PKG_ROOT=/home/safl/.local/share/cijoe
CIJ_EMPH_DEFAULT=
CIJ_TESTSUITES=/home/safl/.local/share/cijoe/testsuites
CIJ_TESTCASES=/home/safl/.local/share/cijoe/testcases
CIJ_ROOT=/home/safl/.local/share/cijoe
CIJ_HOOKS=/home/safl/.local/share/cijoe/hooks

Testcases without runner

When 1 out of 40.000 tests fail, you might want to zoom in and run that testcase manually, here is how you would do that:

# Start cijoe interactively with your test-environment
cijoe box01_env.sh

# Define the test-result root
export CIJ_TEST_RES_ROOT=/tmp/manual

# Then just run the bash-script!
bash "$CIJ_TESTCASES/example_01_minimal.sh"

Note

If your testplan uses hooks, evars, or other target-modifying things, then the state of your target will of course not match the state of your target when the testcase is executed via the runner.