Testing ever changing web code
I am trying to pull together a process for testing a website that has already been released. (QA were introduced to the company 2 years after launch).
The main problem is:
1)The code that is released to QA can be changed in development as soon as it is released to us , therefore if we find problems, the next release of it will contain even more fixes or changes. It has to be like this due to the dynamic nature of the site.
2) One piece of code is so dependent on another that one file broken may affect a dozen more so we cannot release just working files after testing. Also there is nothing documented to show the relationship between files.
3) The company wants to release twice a week
4) The work is fixed and uploaded to a dev machine, checked, then everything is copied to QA, then if it works everything is uploaded to Live. Therefore, we can't just get items for retest released to us.
Any suggestions? My head is going to explode. Visio is going to burn soon I swear!
Re: Testing ever changing web code
Sounds like someone needs to hit the pause button, implement a Configuration Management plan/tool, define a dev->test->promote cycle and then push the play button again.
Sounds easy - I know it isn't, but it is easier than killing production unexpectedly and spending a week finding the "right" code to promote to get back to where you were!
Do you have automated testing tools for regression testing? If you are promoting twice a week, this sounds like a place where automating the most common/stable functions would have a huge payoff.
Sr. Performance Engineer