If you're concerned about regressions specific to the Heroku environment, your best bet might be to write a test suite that makes requests directly to your Heroku-hosted site (presumably you'd want to do this in a staging environment). You could do it at the Selenium layer or just by making HTTP requests from Ruby and making assertions on the responses.
On Fri, Mar 19, 2010 at 09:26, Betelgeuse <[email protected]> wrote: > Heroku is not bug free so it would be useful to be able to run against > the exact environment. > I recently found an issue with Bamboo 1.8.7 not having Kernel#callcc > for example. > > On Mar 19, 2:02 pm, "Matthew A. Brown" <[email protected]> wrote: >> I'm guessing Heroku doesn't intend for you to run your specs on their >> dynos. When you install your app, my impression is that they >> install/modify several config files in your app to make it play nice >> with their environment, all of which are configured for the production >> environment. >> >> What's wrong with just running the specs locally? >> > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
