Home

Checkout the possible future of Protest.

Need examples, background, and link to online rdocs.

TODO

Good lord, TONS OF STUFF! We need help :)

• Documentation
• Refactor reporting; some abstracting is needed for recording a result (for instance)
• Need to know where in backtrace a test failed (line number, etc.); i.e. backtrace filtering for clarity
• More assertion macros: throws, etc.
• Aliases for context “with, without, when, …”; add those words to test description
• Optimization and simplification (ex. flog is complaining print\result\stack)
  • 19.7: TextReport#print_result_stack
  • 19.1: Protest#context
  • 15.9: Context#report
  • 14.2: TextReport#results
  • 13.3: Assertion#actualize
  • 12.5: AssertionMacros#matches
  • 12.3: main#none
  • 12.3: AssertionMacros#raises
• Better error messages?
• Perhaps: Multiple setup blocks in one context
• Perhaps: association macro chaining
• Perhaps: Uhhhhh … a teardown method (only maybe. not sold :)