Skip to content

Issues: thumblemonks/riot

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

8 Open 21 Closed
8 Open 21 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

force a setup to run last feature-request
#39 opened Sep 3, 2011 by ghost
Now that we have denies, let's @deprecate the any macro assertions @deprecate
#26 opened Feb 16, 2011 by gus
1
Now that we have denies, let's @deprecate the exists macro assertions @deprecate
#25 opened Feb 16, 2011 by gus
Add a section on porting tests from shoulda and from rspec to the glamour doc site documentation
#23 opened Jan 25, 2011 by gus
3
Now that not! is deprecated, let's get rid of it assertions
#22 opened Jan 25, 2011 by gus
1
Can Riot optionally support setup/teardown runs per assertion? feature-request
#21 opened Jan 25, 2011 by gus
2
Handle exceptions in setup-like blocks reporting
#19 opened Jan 10, 2011 by gus
Require in files from test/riot_macros feature-request
#9 opened Dec 29, 2009 by thumblemonks
1
ProTip! Add no:assignee to see everything that’s not assigned.