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.)
• Uhhhhh … a teardown method :)
• More assertion macros: kind_of, throws, etc.
• Handle assertion macros better
• Handle denies macro different, so that an entire failure message can translated to the ‘negative’ assertion. I don’t want to add deny_this and deny_that macros
• Optimization and simplification (ex. flog is complaining about the assertion macros)
  • 20.9: AssertionMacros#matches
  • 19.3: AssertionMacros#raises
  • 17.8: AssertionMacros#equals
• Better error messages (maybe need to rename asserts to should for better readability)
• Perhaps: Multiple setup blocks in one context
• Perhaps: association macro chaining