Add a script to test a rails app being made a-fresh.

[fables-tales]

No description provided.

[fables-tales]

This failed for me on master, and passed on the branch I created, so I think it's testing the behaviour we want.

[fables-tales]

This build seems to be stuck in travis's queue, is that normal?

[myronmarston]

I thought our build already did something like this. Does it not?

[fables-tales]

It does, but something about how it gets loaded means that rspec-support has already been required by the time we get to that line of code. This is completely outside of any RSpec launched context and thusly seems to actually detect on the bug.

[myronmarston]

Can we change the existing part of the build to use this then? Seems unnecessary to do this twice in two different ways as part of 1 build.

[cupakromer]

I really appreciate all the help you've done with this @samphippen. I agree with Myron that we should find a way to integrate this with the existing process / fix the existing process. When the build runs, it is supposed to check these things.

There is a Rake task called smoke. I believe this task was intended to catch exactly this, as well as, a very basic app's specs generated through the generators. I'd love to get that properly fixed.

[fables-tales]

Gonna close this in favour of fixing the existing smoke tooling. @cupakromer and I are going to take a look at this over at Ruby Nation.