Currently, make test builds and runs a mess of shell, Python, and Objective-C code, which I've started referring to as the “test monsters”.
There are two test monsters. One of them does not even really test anything; it simply spews a bunch of output and leaves it to the person driving the machine to read it and scan for errors. (You tell me when the last time that actually happened was.) The other does test the output—using diff.
Now that we have (relatively) modern OCUnit-based tests, the test monsters should be slain.
This is blocked until all of the test cases worth caring about from the test monsters are ported over to OCUnit.
Once that's done, the test monsters should be killed off (and good riddance to them), and make test changed to run the Xcode tests.
Currently,
make test
builds and runs a mess of shell, Python, and Objective-C code, which I've started referring to as the “test monsters”.There are two test monsters. One of them does not even really test anything; it simply spews a bunch of output and leaves it to the person driving the machine to read it and scan for errors. (You tell me when the last time that actually happened was.) The other does test the output—using diff.
Now that we have (relatively) modern OCUnit-based tests, the test monsters should be slain.
This is blocked until all of the test cases worth caring about from the test monsters are ported over to OCUnit.
Once that's done, the test monsters should be killed off (and good riddance to them), and
make test
changed to run the Xcode tests.