Home

Checkout the possible future of Protest.

Need examples, background, and link to online rdocs.

TODO

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

1. Documentation
2. Refactor reporting; some abstracting is needed for recording a result (for instance)
3. Need to know where in backtrace a test failed (line number, etc.)
4. Uhhhhh … a teardown method :)
5. More assertion macros: kind_of, throws, etc.
6. Handle assertion macros better
7. 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
8. Optimization and simplification (ex. flog is complaining about the assertion macros)
   1. 20.9: AssertionMacros#matches
   2. 19.3: AssertionMacros#raises
   3. 17.8: AssertionMacros#equals
9. Better error messages (maybe need to rename asserts to should for better readability)
10. Perhaps: Multiple setup blocks in one context
11. Perhaps: association macro chaining