At Skiva we are acutely aware that the ultimate success for a testing project depends predominantly on the test planning and strategy design phase. During this phase, the general objectives and requirements are translated into detailed plans, methods, standards and creation of the testing kits, these being intended for the use of those conducting the testing itself.
We understand that the planning stages are crucial if the results are to be recognized as accurate. The planning process ensures that a high level of efficiency and quality is maintained during the entire process and here at Skiva we carefully review the specs on the product so that unique and specific test documentation can be created and captured. We want to ensure the overall test plan identifies the milestones, interim steps, and requirements for any resources that might be needed during the testing process.
The project scope and expectations must be specific and defining the objectives that are expected is necessary in order to determine whether or not the objectives have been successfully accomplished. The planning process for any testing determines what the test approach should be and how to get there. During the planning process, the technology and methodology will be selected, and the platforms and tools will also be identified and acquired.
Some of the testing may be done automatically, while other tests are performed manually, the sequence of the tests to be performed and the extent of the coverage being defined. In addition, we also understand that the testing process must be linked to the software development cycle, defining the scope of requirements needed is necessary, and identifying any resource augmentation that might be required is another component. Finally, the exact definition of quality analysis must also be in place.
