This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit f74ba37f4e4175d5a1b31da59d161b0020b58e94
tree fee4f0c757d26e5c0355f7ed5c086b1f81c9617a
parent 048ac3604cd46479002eaf7b1bb32770289580fc
tree fee4f0c757d26e5c0355f7ed5c086b1f81c9617a
parent 048ac3604cd46479002eaf7b1bb32770289580fc
... |
... |
|





Comments
Interesting. This is something I had done in my tests that looks somewhat similar. Only that mine can have “unimplemented” tests.
Is there a reason for underscorizing the test names? doing the following is legal and more readable:
@test_name = “test #{name}”.to_sym
@With the current implementation, a test like:
@test “User’s should return [:a, :b] on #to_book?”
@(totally contrived) would produce a method like:
@“test_User’s_should_return_[:a,]_on#to_book?”
@instead of
@test User’s should return [:a, :b] on #to_book?”
@ok, no idea how to format code blocks in github comments :-/
Tammer: I learned that trick from you in shoulda, you nut.