3 ms·
I seriously would like more people to explain their experience if they tried this, but unit test and integration tests are no substitute for QA. Especially for
by minalecs 16y ago
I seriously would like more people to explain their experience if they tried this, but unit test and integration tests are no substitute for QA. Especially for a young startup trying to get traction, I seriously can't see how this is beneficial to have possibly a buggy to low quality app with possibly several bad deployments. How do you avoid the problem of continuously putting out small fires, rather than looking at big picture type problems with this continuous deployment cycles ? Am I misunderstanding the process ?
- prosa 16y agoContinuous Deployment has been a tremendous boon to us at CollegeJobConnect. We make it work by: - Being maniacal about integration tests - Manually testing key flows (user registration in particular) - Hoptoad exception tracking coupled with push email - cap deploy:rollback When you have production database migrations things get a little trickier. We are still looking for better ways to handle migrations in general, including leveraging systems like MongoDB.
- minalecs 16y agoare you manually testing, on your production environments ?
- prosa 16y agoWhen we make significant changes to elements that affect certain critical aspects of our site (a very limited number of specific places, like user registration) we sometimes walk through manually just so we can sleep a bit easier. To date, our test coverage has been sound and we haven't caught anything this way. It may be redundant but we like to see it for ourselves just to be sure.