starship/integration_test
Matan Kushner 8239fbd12b
Refactor integration tests (#71)
- Create subcommands to be able to print modules independently
	- `starship prompt` will print the full prompt
	- `starship module <MODULE_NAME>` will print a specific module
		e.g. `starship module python`
	- Added `--path` flag to print the prompt or modules without being in a specific directory
	- Added `--status` flag to provide the status of the last command, instead of requiring it as an argument
- Refactored integration tests to be end-to-end tests, since there was no way in integration tests to set the environment variables for a specific command, which was required for the `username` module
- Moved e2e tests to `tests/testsuite` to allow for a single binary to be built
	- Tests will build/run faster
	- No more false positives for unused functions
- Added tests for `username`
- Removed codecov + tarpaulin 😢
2019-06-06 13:18:00 +01:00

17 lines
475 B
Bash
Executable File

#!/bin/bash
if ! (docker --version); then
printf 'Docker is required to run the starship integration tests.\n'
printf 'Please download and install Docker in order to run these tests locally.\n'
exit 1
fi
printf 'Building test docker image:\n'
docker build -f tests/Dockerfile \
--tag starshipcommand/starship-test \
--cache-from starshipcommand/starship-test \
.
printf 'Running test suite:\n'
docker run --rm -v $(pwd):/starship starshipcommand/starship-test