Conversation
jonmcalder
left a comment
There was a problem hiding this comment.
Thanks.
If you'd like to update the tests for this exercise, then please align the changes to match the tests outlined in the problem specifications repo
Track tests do fall out of sync with what's specified (as has happened here), but we generally try not to deviate from those tests unless there is a track-specific or language-specific reason to do so.
|
I think I'll close this down. It looks like the specification has duplication meaning these tests would need to reflect that. Test cases are immutable with only description, comments or scenario additions being allowed.
So every language track needs to implement redundant tests to align with this problem specification. It makes sense to make them immutable so the many dependant language tracks don't fall out of alignment and aren't routinely having to sync. But the OCD in me has a little eye twitch while reading this specification 😄 Duplicate test example (the candidates input are slightly different but from a test perspective I would call them identical). |
|
Oh... wait I just noticed the field |
I tried to open this a few months ago during a hiatus. Reopening again 🤞🏽 #233
Going through this exercise I notice a fair bit of redundant testing. They loose value when duplicated and make it harder to establish the expected result.
Removed multiple tests for "detects multiple anagrams"
Removed multiple tests for "anagrams must use all letters exactly once"
Removed multiple test for "case insensitive checking"
Clarified test descriptions