Skeletal Test Suite

[digitalextremist]

Basic foundation for test-suite, focusing to start-with on base objects.

(checklist by benzrf)

• Enumerate stuff to test.
• Enumerate testable behavior in each thing.
• Write tests.

[sarahzrf]

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?

[digitalextremist]

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 ).

[sarahzrf]

Stuff to test:

• Color
  • Wrote some tests already
• Line
  • Wrote some tests already
• Spool (if we're even keeping Spool around)
  • TODO
• Frame
  • Provisioning
  • Event publishing
  • Startup and shutdown
• Logger (module in Internals)
  • Difficult to test because so much stuff calls into it. It's hard to isolate.
• Figure
  • Face initialization
  • Line initialization
  • Event handling
• Management
  • Manage
    • Can issue instructions and wait for replies
    • Leader automaton functions correctly
  • Cooperate
    • Executes instructions and replies
    • Follower automaton functions correctly
  • Administrate
    • I'm not personally clear on what this is supposed to do, once implemented.
• Awareness
  • Notice
    • Reports
  • Announce
    • Heartbeats and presences
• Vitality
  • Correctly handles an attaching follower
  • Sends out pings
  • Correctly handles a follower dying
  • Utility methods work as expected
• Logging (shape in Base)
  • Run under an ID other than :logging so that it doesn't get logged to by normal code.
  • Collate
    • Prints logs
  • Document
    • Sends logs
  • Relay
    • Relays logs
• Calling
  • Answer
    • Answers calls
  • Switch
    • Switches calls
  • Call
    • Places calls
• Distribution
  • Distribute
    • Distributes (and collects?) tasks
  • Process
    • Pulls tasks
    • Reports results
• Certain Figure interactions - need to work this out.
  • TODO

Do we need tests for the Sketches from Ef? They don't seem to be core ECell functionality.

[sarahzrf]

@digitalextremist Just how skeletal can I get away with this being?

[sarahzrf]

OK, I've added it clauses for each of the behaviors outlined above. How much do i need to fill them in with?