Software testing methodology
Methodology of MassQA
During our outsourcing testing business we have found that it is impossible to have a unified approach to every project. Large projects should have more detailed level of processes and complexity than small ones. Small projects could have no formal processes at all however project could be very successful. However, both large and small projects have to be controlled at each project phase to avoid problems or solve them rapidly.
The base methodology of our company is Rational Unified Process (RUP). Having customer orientation as the main aim our methodology could be modified for each customer to satisfy project needs. It makes our customers feel absolutely comfortable.
Requirements Management
The project is the most successful if it has clear and detailed requirements to all features and usage configurations. Testing team should understand what is expected at each point of application and project. In cases when it is impossible to have these requirements we could provide you with Business Analyst for tight cooperation with customer representative.
Project Management
There should be contact points at each side ? local project manager or team lead and representative on customer's side. Besides that all timelines and delivery dates should be defined. We use Microsoft Project as a project management system. We are trying to make the process as transparent as it is possible.
Defects Management
Defects (also called 'bugs') should be notified to developers to be fixed. Using bug-tracking system is thought to be optimal solution. We provide BugZilla bugtracker as it is the simplest application and it has all necessary features. We could use local bug-tracker and share that with you or wise versa, use bug-tracker on your site.
Configuration Management
Standard solution for document versions control is using CVS. This tool is excellent for remote interaction with customer repository and could easily revert to previous state.
Back to top
