almalinux/lorax
13
0
Fork 0
Code Issues Pull Requests Releases Activity
ed15b81818
lorax/tests/cli/test_compose_sanity.sh

56 lines
1.8 KiB
Bash
Raw Normal View History

New cli test covering basic compose commands - need to specify --sharedir so lorax-composer can find its kickstart files - each test script writes results into a separate directory to avoid a passing test overwriting the results from a failing one. To avoid reporting failures in case of previously failing tests (e.g. during development) remove the temporary directories holding tets results before execution!
2018-09-21 09:46:54 +00:00
#!/bin/bash
# Note: execute this file from the project root directory
tests: Fail on script errors Fixes #727
2019-06-02 13:20:42 +00:00
set -e
New cli test covering basic compose commands - need to specify --sharedir so lorax-composer can find its kickstart files - each test script writes results into a separate directory to avoid a passing test overwriting the results from a failing one. To avoid reporting failures in case of previously failing tests (e.g. during development) remove the temporary directories holding tets results before execution!
2018-09-21 09:46:54 +00:00
. /usr/share/beakerlib/beakerlib.sh
Monkey-patch beakerlib to fail on first assert Beakerlib upstream can't do this yet, but might at some point: https://github.com/beakerlib/beakerlib/issues/42 This is only enabled in combination with the `--sit` option of the `test/check-*` scripts. It leaves the system in exacly the state it was in when an assertion failed. Finishing the test run would run cleanup as well (such as deleting created images). It also takes longer.
2019-06-02 13:08:03 +00:00
. $(dirname $0)/lib/lib.sh
New cli test covering basic compose commands - need to specify --sharedir so lorax-composer can find its kickstart files - each test script writes results into a separate directory to avoid a passing test overwriting the results from a failing one. To avoid reporting failures in case of previously failing tests (e.g. during development) remove the temporary directories holding tets results before execution!
2018-09-21 09:46:54 +00:00
Allow overriding $CLI outside test scripts this will allow you to test against installed RPM like so: # export CLI="/usr/bin/composer-cli" # make test_images If you already have lorax-composer running then you can directly execute test scripts: # ./tests/cli/test_build_and_deploy_aws.sh
2019-03-08 10:29:11 +00:00
CLI="${CLI:-./src/bin/composer-cli}"
New cli test covering basic compose commands - need to specify --sharedir so lorax-composer can find its kickstart files - each test script writes results into a separate directory to avoid a passing test overwriting the results from a failing one. To avoid reporting failures in case of previously failing tests (e.g. during development) remove the temporary directories holding tets results before execution!
2018-09-21 09:46:54 +00:00
rlJournalStart
rlPhaseStartTest "compose types"
composer-cli: Only display the available compose types The enabled bool is now being used so the cli should only show the types actually available on the architecture. Also modifies the test in test_compose_sanity.sh Related: rhbz#1751998
2019-12-10 19:34:42 +00:00
if [ "$(uname -m)" = "x86_64" ]; then
rlAssertEquals "lists all supported types" \
"`$CLI compose types | xargs`" "alibaba ami ext4-filesystem google hyper-v live-iso liveimg-tar openstack partitioned-disk qcow2 tar vhd vmdk"
else
# non-x86 architectures disable alibaba
rlAssertEquals "lists all supported types" \
"`$CLI compose types | xargs`" "ext4-filesystem live-iso liveimg-tar openstack partitioned-disk qcow2 tar"
fi
New cli test covering basic compose commands - need to specify --sharedir so lorax-composer can find its kickstart files - each test script writes results into a separate directory to avoid a passing test overwriting the results from a failing one. To avoid reporting failures in case of previously failing tests (e.g. during development) remove the temporary directories holding tets results before execution!
2018-09-21 09:46:54 +00:00
rlPhaseEnd
rlPhaseStartTest "compose start"
UUID=`$CLI --test=2 compose start example-http-server tar`
rlAssertEquals "exit code should be zero" $? 0
UUID=`echo $UUID | cut -f 2 -d' '`
rlPhaseEnd
rlPhaseStartTest "compose info"
if [ -n "$UUID" ]; then
rlRun -t -c "$CLI compose info $UUID | egrep 'RUNNING|WAITING'"
else
rlFail "Compose UUID is empty!"
fi
rlPhaseEnd
rlPhaseStartTest "compose image"
[tests] Use a function to wait for compose to finish The function is meant to replace the duplicate pieces of code used in various tests, the polling interval is unified to 20 seconds.
2019-09-06 16:56:19 +00:00
wait_for_compose $UUID
New cli test covering basic compose commands - need to specify --sharedir so lorax-composer can find its kickstart files - each test script writes results into a separate directory to avoid a passing test overwriting the results from a failing one. To avoid reporting failures in case of previously failing tests (e.g. during development) remove the temporary directories holding tets results before execution!
2018-09-21 09:46:54 +00:00
if [ -n "$UUID" ]; then
tests: Add check to make sure the compose actually finished Previously it was looping, waiting for FINISHED|FAILED but was not actually failing the test if the compose failed to build. This adds a function to check the status of the compose and calls it after each compose.
2019-07-10 15:58:24 +00:00
check_compose_status "$UUID"
New cli test covering basic compose commands - need to specify --sharedir so lorax-composer can find its kickstart files - each test script writes results into a separate directory to avoid a passing test overwriting the results from a failing one. To avoid reporting failures in case of previously failing tests (e.g. during development) remove the temporary directories holding tets results before execution!
2018-09-21 09:46:54 +00:00
rlRun -t -c "$CLI compose image $UUID"
rlAssertExists "$UUID-root.tar.xz"
Add new test to verify compose paths exist because they are mentioned in the official documentation
2019-04-08 09:12:28 +00:00
# because this path is listed in the documentation
rlAssertExists "/var/lib/lorax/composer/results/$UUID/"
rlAssertExists "/var/lib/lorax/composer/results/$UUID/root.tar.xz"
rlAssertNotDiffer "/var/lib/lorax/composer/results/$UUID/root.tar.xz" "$UUID-root.tar.xz"
New cli test covering basic compose commands - need to specify --sharedir so lorax-composer can find its kickstart files - each test script writes results into a separate directory to avoid a passing test overwriting the results from a failing one. To avoid reporting failures in case of previously failing tests (e.g. during development) remove the temporary directories holding tets results before execution!
2018-09-21 09:46:54 +00:00
fi
rlPhaseEnd
rlJournalEnd
rlJournalPrintText
Reference in New Issue Copy Permalink