Test planning, it’s that task testers are often asked to perform at short notice and frequently without enough information. It’s something that sounds like it should be easy, but all too often turns into something more challenging. As testers, we also find that we sometimes become accountable based on a test plan that was formed in a hurry without enough information to begin with. Is there anything we can do to avoid this?
The Different Phases of Software Testing
Testing can be thought of as the backbone of every software development project. It’s not hard to see why testing has a place in each part of the System Development Life Cycle (SDLC). Employing a poor testing methodology will potentially lead to the production of an unstable system and most likely, one that will cost you more money and time to put right.
Within every organisation there are a number of documents that have a hieratical order. When it comes to testing you would expect to find the Test Policy document at the top of the tree; this document is only a couple of pages long but does at executive level spell out the quality needs of the organisation and gives the vision of what is expected of every project. This document is owned by the CIO or IT Director and should be mandated to ensure every programme and project works to the same expected standards every time.