ef7470e5da
run_tests.sh was created as an entry point for bashate. We stopped
using it now that we know how to run bashate directly in the gate.
We lost running an unrelated bashate test when that happened.
Devstack does have unit tests. We don't run them. We should.
Especially when working on things like the LIBS_FROM_GIT which is
sufficiently tricky that we really need to add unit tests to ensure
that we don't break it.
Conflicts:
run_tests.sh
Change-Id: Ife067855569e2eae4c085471d326e8086de37332
(cherry picked from commit 9f20ea1382)
45 lines
1.2 KiB
Bash
Executable File
45 lines
1.2 KiB
Bash
Executable File
#!/bin/bash
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
# License for the specific language governing permissions and limitations
|
|
# under the License.
|
|
#
|
|
#
|
|
# this runs a series of unit tests for devstack to ensure it's functioning
|
|
|
|
PASSES=""
|
|
FAILURES=""
|
|
|
|
# Test that no one is trying to land crazy refs as branches
|
|
|
|
for testfile in tests/test_*.sh; do
|
|
$testfile
|
|
if [[ $? -eq 0 ]]; then
|
|
PASSES="$PASSES $testfile"
|
|
else
|
|
FAILURES="$FAILURES $testfile"
|
|
fi
|
|
done
|
|
|
|
# Summary display now that all is said and done
|
|
echo "====================================================================="
|
|
for script in $PASSES; do
|
|
echo PASS $script
|
|
done
|
|
for script in $FAILURES; do
|
|
echo FAILED $script
|
|
done
|
|
echo "====================================================================="
|
|
|
|
if [[ -n "$FAILURES" ]]; then
|
|
exit 1
|
|
fi
|