5 ms·
How do you make sure the correctness of the implementations? Shouldn't there be tests?
by cmpitg 13y ago
How do you make sure the correctness of the implementations? Shouldn't there be tests?
- kennyledet 13y agoPrecisely. This is something that I have plans on implementing, but obviously I don't have the whole day 24/7 to manage this repo man. I'm doing other things right now (work), that's why I took so long to even answer the initial comments in this thread.
- ericHosick 13y agoTests and behavior should be defined before the code. I recommend you comment out all code, write the tests and then un-comment the code line by line. This not only tests the code, but tests the tests and assures that you are covering the edge cases the code contains already.
- kennyledet 13y agoUpdate: Unit tests are now a convention.
- goldenkey 13y agoThe code is the test. If the code runs without compilation errors, then use it for healthcare.gov </sarcasm>
- kennyledet 13y agoYou forgot to open the the sarcasm tag :)
- goldenkey 13y agoThat's part of the hidden DOM. Implicit. ;-)
- kennyledet 13y agoSorry, but explicit > implicit for markup. Btw, how's that repo going? :)
- goldenkey 13y agoSorry, haven't started it yet ;-)