61c5df7c11
This commit changes the way the extended test suite is run. Previously, there was a folder full of outputs, and a script that ran exa repeatedly to check the outputs match. This script was hacked-together, with many problems: • It stops at the first failure, so if one test fails, you have no idea how many actually failed. • It also didn't actually show you the diff if one was different, it just checked it. • It combined stdout and stderr, and didn't test the exit status of exa. • All the output file names were just whatever I felt like calling the file at the time. • There is no way to only run a few of the tests — you have to run the whole thing each time. • There's no feel-good overall view where you see how many tests are passing. I started writing Specsheet to solve this problem (amongst other problems), and now, three and a half years later, it's finally ready for prime time. The tests are now defined as data rather than as a script. The outputs have a consistent naming convention (directory_flags.ansitxt), and they check stdout, stderr, and exit status separately. Specsheet also lets simple outputs (empty, non-empty, or one-line error messages) can be written inline rather than needing to be in files. So even though this pretty much runs the same tests as the run.sh script did, the tests are now more organised, making it easy to see where tests are missing and functionality is not being tested.
2.3 KiB
exa › xtests
These are the extended tests. They are integration tests: they run the exa binary with select configurations of parameters and environment variables, and assert that the program prints the correct text to standard output and error, and exits with the correct status code.
They test things like:
- broken symlinks
- extended attributes
- file names with weird stuff like newlines or escapes in
- invalid UTF-8
- missing users and groups
- nested Git repositories
They are intended to be run from the Vagrant VM that has already had its environment set up — see the devtools/dev-create-test-filesystem.sh script for how the files are generated.
Anatomy of the tests
The tests are run using Specsheet. The TOML files define the tests, and the files in output/ contain the output that exa should produce.
For example, let’s look at one of the tests in lines-view.toml. This test checks that running exa does the right thing when running with the -1 argument, and a directory full of files:
[[cmd]]
name = "‘exa -1’ displays file names, one on each line"
shell = "exa -1 /testcases/file-names"
stdout = { file = "outputs/names_lines.ansitxt" }
stderr = { empty = true }
status = 0
tags = [ 'oneline' ]
Here’s an explanation of each line:
-
The
[[cmd]]line marks this test as a cmd check, which can run arbitrary commands. In this case, the commad is exa with some arguments. -
The
namefield is a human-readable description of the feature of exa that’s under test. It gets printed to the screen as tests are run. -
The
shellfield contains the shell script to execute. It should haveexain there somewhere. -
The
stdoutfield describes the content that exa should print to standard output. In this case, the test asserts that the output of running the program should be identical to the contents of the file. -
The
stderrfield describes the content of standard error. In this case, it asserts that nothing is printed to stderr. -
The
statusfield asserts that exa should exit with a status code of 0. -
The
tagsfield does not change the test at all, but can be used to filter which tests are run, instead of running all of them each time.