Hardcoded data will pass the test.

I'm pretty vocal against "The Rails Way," especially its testing, so I just wanted to show one way that I can break your Rails app with the tests still passing.

Again, when the tests run through the request cycle, a lot of distance is put between the code you're trying to test and the actual test.  Rails devs often deal with this by dropping tons detail, including verifications that the tests are actually doing what they say they are doing.  Tests like "The X is shown on the page" when all they do is assert that a name of one of their test objects appears on the page.

It's another reason I advocate for unit testing, which will actually cover the code you mean to cover.

https://github.com/nerdbeers/nerdbeers/pull/29