A few weeks ago I found a javascript bug that was really just a silly mistake by the developer, but it was one that could have easily gone undetected. I found it because when I run the app locally, I always run it at this url:
http://localhost:3000/trisano
This dev runs the app like this:
http://localhost:3000
His javascript made assumptions about the url that were never-false when run his way, but were immediately broken when run mine.
So, while this probably sounds like a simple thing, it’s a good,routine practice to NOT run the application you’re testing just like the developers do. I’m not talking only about the url you run it at, but consider using any other options that are available in a production deployment of your app that are not used by devs and consider including them in your testing routine.
If you enjoyed this post, make sure you subscribe to my RSS feed!
Stumble it!
2 responses so far ↓
1 adam goucher // Nov 2, 2009 at 12:02 pm
Have you given any thought to having a separate 'david' environment to help manage these things? You could then start playing with caching and other settings in a sandbox and not worry about committing production.rb with one of your tweaks.
-adam
2 davidray // Nov 2, 2009 at 12:49 pm
That's a good idea Adam. I think I'll mess around with that. When I test our Enterprise Edition version I don't have to worry about that because the build process creates a working copy that is outside of git, but it's an issue with our Community Edition.
Leave a Comment