How to structure automated testing on a brand new app?
I'd like to tap your knowledge, and ask for some of your advice.
We are rewriting our application from the ground up (again). We are switching over from a pure Unix based system to a Client/Server model. This is a very large application with (probably) one million + of lines of code. We're starting from scratch. <- Moderator, forgive me for this blatant copy/paste job from my previous post.
My question is, how would I go about creating an environment where people are cognoscente of the fact that automated testing will be an important part of this project?
In other words, we are currently creating the architecture and doing a proof of concept for this HUGE project, and I'd like to make sure automation is part of this. Do you have any suggestions as to what I should do to keep this application going in the right direction from the very start, from an automation point of view?
Compared to other companies, I think our "automated testing culture" is relatively lacking. It is getting better, but we've still got a long way to go. Are there any lessons learned that anyone would care to share with me on a project of this magnitude?
Re: How to structure automated testing on a brand new app?
Without knowing the structure of your QA department I'll assume it is similar to ours. I would ask for a one-on-one with first your Director of QA, or the top person. Explain that with a project of such magnitude it would be a real credit to the department to get automation involved on the ground floor. Once the test plan begins to take shape jump in there and suggest ways that automation can handle different function points in the testing allowing the manual testers to concentrate on test case writing and new functionality. Stress that if ever there is a plan for determining an ROI for automation then this is it! Also one-on-one with the project manager explaining that, for the same reasons, automation would be beneficial for meeting deadlines and helping stabilize the project for the long haul. Automation is just another tool in the QA's bag of tricks and is only as good as it is allowed to be. But if the company has gone through the expense and learning curve to get automation up and running then by golly they should have some confidence in it allow it to help the overall process.
Success is the ability to go from one failure to another with no loss of enthusiasm.
~ Winston Churchill ~