-
-
Notifications
You must be signed in to change notification settings - Fork 658
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure consistency across exercise tests #470
Comments
List of all exercises, to be checked individually for consistency and ticked off when meeting the above conditions.
|
acronym is already ok...wait no, needs fatalf |
changed test version check error to fatal in acronym, see #470
wordy: add test versioning, see #470
word-search: extract TestTestVersion function (#470)
luhn: move TestTestVersion to be first test (#470)
allergies: extracted test version test as its own function, see #470
atbash-cipher: added test versioning, see #470
anagram: added test versioning, see #470
bank-account: added test versioning, see #470
binary-search-tree: added test versioning, see #470
* Moved TestVersionTest to start of test functions see #470
I believe this is accomplished? 🍀 😄 |
@tleen you're a test consistency powerhouse! 💪 Well done for finishing this off. |
Good stuff. I'll close this one out. 👍 |
Nice work doing this for all 80 of our exercises! (Plus the deprecated ones, I believe that makes it 85) If y'all are thinking of other things to do, could consider ensuring that all exercises in x-common that have canonical-data.json have a test generator, and that the test generators still run (due to recent schema changes, some generators might require changes). This can help our track more easily keep up with changes to x-common (just rerun the generator, and we are done!). No obligation to take this suggestion, since I don't consider myself to hold any special authority here; just whatever makes our lives as maintainers easier. |
Sure. I'm sort of swamped at work till mid-April but if you make an issue for this we can slowly work our way through it like with the test versioning. |
I'd been thinking this same thing. I'll make a start on it in the coming weeks also. |
OK. I can't start to make the issue for the next 4 hours. I will do it after that, unless one of you says you are before then. |
#465 highlighted certain test file inconsistencies between the exercises.
These were:
testVersion/targetTestVersion
for all exercises, initialised at 1, to be incremented upon significant changesTestTestVersion
function, rather than as part of main test functionTestTestVersion
function as the first test functionTestTestVersion
function usingFatalf
rather thanErrorf
The text was updated successfully, but these errors were encountered: