|
At Octopus we believe that developers are responsible for finding errors before they reach testing, and testers are responsible for finding errors before they reach the customer.
All this requires a disciplined approach to development. It means developing a culture, a point of view or set of values shared by the development team where developers have a sense of ownership for their work and are constantly finding ways to improve the way that they do their work. It means putting in place the necessary quality controls to ensure that mistakes are avoided, or found and corrected before the customer finds them.
Our Quality Plan addresses all phases of the development process. It includes in-process controls and practices such as:
- A clearly defined process for capturing the business goals for the project and the product feature set in partnership with the customer
- Minimization of the expectation gap between what the customer wants and what the development team delivers
The secret behind Octopus’s bug free products depends on the regression test banks and checklists to prevent errors from creeping into the product later in the development cycle.
Main components of the Octopus’s Quality Plan include:
- The Development of Test Cases on the basis of the Clarify Document
- Actual Testing based on Test Cases
- Unit and Integrated based Procedures of testing
- Bug Stating Procedures
- Bug Handling Procedures
- Bug Reports and Change Control Procedure:
 Software Change Control Requests and Reports
Software Trouble Reports
- Maintain Logs and Records
- Manuals and User Documentation
|
