Llewellyn/exa
1
0
Fork 0
mirror of https://github.com/Llewellynvdm/exa.git synced 2024-11-12 23:46:30 +00:00
Code Issues Projects Releases Wiki Activity
61c5df7c11
exa/devtools
History
Benjamin Sago 61c5df7c11 Use Specsheet for the extended tests 
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.
2020-10-17 21:12:18 +01:00
..
dev-bash.sh Just straight-up roll our own logger 2020-10-10 02:01:12 +01:00
dev-create-test-filesystem.sh Use Specsheet for the extended tests 2020-10-17 21:12:18 +01:00
dev-fixtures.sh Make the Vagrant environment creation nicer 2020-10-16 23:41:25 +01:00
dev-help.sh Change user in Vagrantfile 2018-09-26 21:25:50 +01:00
dev-package-for-linux.sh build: use binary name only 2020-07-24 09:03:57 +05:00
dev-run-debug.sh Show friendlier warnings when binaries don’t exist 2017-10-02 10:22:50 +02:00
dev-run-release.sh Show friendlier warnings when binaries don’t exist 2017-10-02 10:22:50 +02:00
dev-set-up-environment.sh Make the Vagrant environment creation nicer 2020-10-16 23:41:25 +01:00
dev-versions.sh Move the welcoming text to their own files too 2017-10-01 09:49:45 +02:00
local-package-for-macos.sh Copy weekly changes into macos script 2017-10-08 20:54:18 +01:00
README.md Vagrant changes 2020-10-10 00:21:20 +01:00

README.md

exa › development tools

These scripts deal with things like packaging release-worthy versions of exa.

They are not general-purpose scripts that you’re able to run from your main computer! They’re intended to be run from the Vagrant machine.