mirror of
https://github.com/GSA/notifications-admin.git
synced 2026-02-13 23:14:32 -05:00
1a353d90eb
Turns out our tests spent a lot of time recreating the app for each test case, which is quite intense. This commit makes the fixture sessions level, so the app is only created once per test session, not once per test function. This cuts down the time taken to run the test suite to about 50 seconds. It also makes the tests more parallelizable. Before this change going from 4 to 8 processes made the tests slower. Now it cuts them down from about 50 seconds to about 35 seconds[1]. So this commit also lets Pytest choose the best number of processes to run, since on my machine it chooses 8, which is the fastest. Overall this means the 1. With a 2.2GHz quad-core Intel Core i7 processor on a 2015 MacBook Pro
42 lines
872 B
Bash
Executable File
42 lines
872 B
Bash
Executable File
#!/bin/bash
|
|
#
|
|
# Run project tests
|
|
#
|
|
# NOTE: This script expects to be run from the project root with
|
|
# ./scripts/run_tests.sh
|
|
|
|
set -o pipefail
|
|
|
|
function display_result {
|
|
RESULT=$1
|
|
EXIT_STATUS=$2
|
|
TEST=$3
|
|
|
|
if [ $RESULT -ne 0 ]; then
|
|
echo -e "\033[31m$TEST failed\033[0m"
|
|
exit $EXIT_STATUS
|
|
else
|
|
echo -e "\033[32m$TEST passed\033[0m"
|
|
fi
|
|
}
|
|
|
|
if [[ -z "$VIRTUAL_ENV" ]] && [[ -d venv ]]; then
|
|
source ./venv/bin/activate
|
|
fi
|
|
|
|
make test-requirements
|
|
display_result $? 1 "Requirements check"
|
|
|
|
flake8 .
|
|
display_result $? 1 "Code style check"
|
|
|
|
isort --check-only -rc ./app ./tests
|
|
display_result $? 2 "Import order check"
|
|
|
|
npm test
|
|
display_result $? 3 "Front end code style check"
|
|
|
|
## Code coverage
|
|
py.test -n auto --maxfail=10 --cov=app --cov-report=term-missing tests/ --junitxml=test_results.xml --strict -p no:warnings
|
|
display_result $? 4 "Code coverage"
|