I will let Aldrin and Arman cover the how's and why's, my main concern right now is that this does not happen again. Last week we had a snafu with the Worthopedia when code was pushed to production and not confirmed. Now we have the same issue with data loading.
EVERYTHING PUSHED TO PRODUCTION WILL BE TESTED.
There will be nothing pushed to production that is not tested at various levels. Developers will test their code as its written and definitely before checking it into Subversion. Data loaders will check logs and ensure the scripts completed successfully. If your code or work is pushed to the production side then YOU are responsible for checking the public site.
We are adding QA resources to the team to act as an independent set of eyes. In no way will this reduce the amount of testing required during (and after) development.
Do not trust logs, script output or anyone else when it comes to your code. Test it yourself, if it fails you will be the one I come to talk to.
I welcome conversation about ways to improve the quality of our product. I am open to hearing anyone's ideas about improving quality.
Testing is the Answer by marcbenton
Thanks for bringing this up here Andy.
I will let Aldrin and Arman cover the how's and why's, my main concern right now is that this does not happen again. Last week we had a snafu with the Worthopedia when code was pushed to production and not confirmed. Now we have the same issue with data loading.
EVERYTHING PUSHED TO PRODUCTION WILL BE TESTED.
There will be nothing pushed to production that is not tested at various levels. Developers will test their code as its written and definitely before checking it into Subversion. Data loaders will check logs and ensure the scripts completed successfully. If your code or work is pushed to the production side then YOU are responsible for checking the public site.
We are adding QA resources to the team to act as an independent set of eyes. In no way will this reduce the amount of testing required during (and after) development.
Do not trust logs, script output or anyone else when it comes to your code. Test it yourself, if it fails you will be the one I come to talk to.
I welcome conversation about ways to improve the quality of our product. I am open to hearing anyone's ideas about improving quality.