Open digitalextremist opened 8 years ago
How fleshed-out does this need to be, and which stuff do I need to have tests for, by the end of GSoC? E.g., do I need to write tests for the Piece startup process as a whole? for parsing Designs? for any multi-Piece interactions?
Celluloid
convention is TDD
so there is a tacit expectation that there be tests for everything.
You seemed shocked by this. At the very least, all the tests need to be setup, but kept pending
or xit
or equivalent. This is an unfortunate compromise.
Ideally, all tests for all objects and all processes would be in the repository before code was originated/migrated. So after the outline of bypassed tests are done, and all the other items on your roadmap, complete as many tests as you can ( and then do more ).
Stuff to test:
Internals
)
Base
)
:logging
so that it doesn't get logged to by normal code.Do we need tests for the Sketches from Ef? They don't seem to be core ECell functionality.
@digitalextremist Just how skeletal can I get away with this being?
OK, I've added it
clauses for each of the behaviors outlined above. How much do i need to fill them in with?
Basic foundation for test-suite, focusing to start-with on base objects.
(checklist by benzrf)