| || |
To set up a testing process
If you're incharge of setting up a testing process and executing regression testing from the business point of view, In a nutshell, what are the key aspects one needs to ensure while setting this up and executing for the first time.
This will involve defining and streamlining a process. From a testing perspective, what are the general loopholes one should keep in mind and plan to avoid? Also, what should the plan cater to in priority?
Re: To set up a testing process
There are no magic, quick answers for this, because it depends on the company. There is no "standard" or "recommended" template.
The first thing you need to do is perform an assessment. This means you need to interview all affected parties and review the assets currently produced by the IT Team. As you gather information from executive management as to what they expect, management staff in regards to what areas have problems and what they feel is going right/wrong, and key individuals in regards to how they do their jobs and how they feel the process should flow, you will find patterns emerging.
The general rule of thumb is to "find out where it hurts" and produce a document that provides a list of problems areas and potential short-range and long-range solutions.
You then sit down with management and put those items in priority. This forms a "roadmap" for implementing a QA/QC function.
Change is implemented according to the roadmap.
Doing things this way will get you more support for your changes, because you will be specifically addressing problem areas reported to you by the IT organization and executive management.
I have found that in companies that have nothing, putting some organization around the testing process, no matter how weak, and implementing a defect management process are good first steps, but again, it depends on the organization and what they want and perceive as critical needs.