I don't like having to manually verify that second+later tests are ignored. Can it be automated?

[petertseng]

As noted in #279, we ignore all tests except the first.

I don't like having to check by hand whether every new exercise submission has done this.

Maybe we can automate it We are automating it in #361 by counting the number of #[ignore] lines and ensuring that it is exactly one smaller than the number of #[test] lines.

By suggestion of a contributor (not myself) another possible way to do it is to run cargo test and make sure it says 1 passed; 0 failed. One disadvantage is it involves having to actually compile and run, whereas counting ignore and test does not.

All current exercises have been fixed so they have exactly one fewer ignore line than test line.

The remaining task is to add it to Travis CI so that future exercises also receive its benefit.

[f3rn0s]

I had a think.

Here is a shell script that will return whether the given file name is valid.

#Argument 0
file_name="$1"

#Number of tests
test_num=$(cat $file_name | grep "\#\[test\]" | wc -l)

#Number of ignores
ignore_num=$(cat $file_name | grep "\#\[ignore\]" | wc -l)

#Number of tests minus 1 should be the number of ignores
compare=$(($test_num - 1))

#Print logic
if [ "$compare" -eq "$ignore_num" ]
then
    echo true
else
    echo false
fi

[petertseng]

Current:

./exercises/bob/tests/bob.rs: Has 25 tests and 23 ignores (should be 24)
./exercises/crypto-square/tests/crypto-square.rs: Has 8 tests and 0 ignores (should be 7)
./exercises/say/tests/say.rs: Has 18 tests and 15 ignores (should be 17)

[petertseng]

Updated issue description: The script exists, and current exercises have been fixed. Next step, if the script receives approval and gets merged, is to add it to Travis CI.