In this post, I will describe test design document and test policy document. I will also discuss about Standards to be followed in Test Analysis and Design, Standard to be followed in Test case specifications (Test Case document) and why Standard is not followed in software testing documentation.
What is Test Design?
Test Design is a document which will be containing tangible test conditions and test cases converted from testing objectives. Also we can say that designs are created from issues which maximum number of end users will be facing with minimal testing.
Test design document will be having information about the software and will also have which business it will be useful. It will also have which functionality to be tested and what kind of testing technique to be used. Properly designed test design document will be helpful in effective testing.
What are Test Procedures and how to ensure test procedures are ready for execution?
Test procedures are organized test cases in a such a way that what all steps are involved in carry out testing will be clear and also what test to be executed in what sequence in with what data, in which environment, and by whom.
To ensure test procedures are ready for execution we need to evaluate the pre-requisites which would need to the execution of test procedures in a specific sequence. We can say test procedures are ready to for execution when:
- Test cases should be prepared and reviewed.
- Order of test procedures to be executed is finalized which will be getting approval from client and informing testers.
- Prioritizing test cases for automation if automation testing will be performed.
- Test harness should be ready and available for testing.
- Identifying the dependencies among test procedures.
- Develop a contingency plan if any of the dependency is not fulfilled.
- Test environment is ready and available and test procedures to executed on that environment should be available for execution.
- Test data available for test procedures.
What is Test Policy Document?
Test policy document is high level document describing about the principles, approaches and prime objectives of organization regarding testing. It will be available at top hierarchy of test documentation structure. It is to showcase the testing philosophy which will act a guideline for testing department to follow and to adhere to it. Test policy can be same or different for new projects and for maintenance projects.
Test policy enlightens about below mentioned factors:
- Definition of testing: It is very much important to define testing and should be made clear to everyone that why they are testing. By defining testing it will be easier to jot down the testing techniques which will be used for testing. When it is clear about testing then it will be more easier to define the purpose of testing.
- Defining test process: It is very much important to identify, tailor and implement a testing process which will help in identifying what type of testing to be performed in what phase. What roles are involved in different types of testing in different phases and what type testing level to be considered.
- Test Evaluation: Once testing test process is identified and implemented then we also need to have test evaluation also. Test evaluation is necessary to ensure the effectiveness of testing in a project.
- Quality Level to be achieved: What is quality we want to achieve which means upto what quality level application should be tested.
- Test Improvement approach: We need to identify when we will be evaluating the effectiveness to testing process.
Standard to be followed in Test Analysis and Design:
Test design specification will be a collection of test cases and will be having test conditions to be covered at a very high level. Collection of test cases in Test Design Specification document is called as Test Suite. Sequence to be followed to test suite is dependent upon risk factors, of business, constraints (technological), resources and progress of project. Test design template will be having following sections:
- Test design specification identifier (containing standards followed in one’s company for document identification)
- Features to be tested.
- Features not be tested. (Out of scope functionalities)
- Any specific tools or techniques or technology to be used.
- Pass/ Fail criteria
Standard to be followed in Test case specifications (Test Case document):
Sections in Test case document are as mentioned below:
- Test case specification identifier.
- Test items. ( Deliverables to be tested)
- Test case Input (Test data, input files for execution of test case.)
- Test case Output (Expected result after execution of test case)
- Environmental specification. (Hardware and software specifications for the execution of test case)
- Pre requisites. (Conditions to be satisfied before execution of test case)
Why Standard is not followed in software testing documentation?
Even is IEEE have define certain standard to be followed for documentation but still in real world those standard are not in use because of the below mentioned factors:
- Risks incurred in project by following proper documentation.
- Value addition by implementing proper documentation.
- Only mandatory specification to be followed.
- Depending on software development life cycle. Agile methodology tries for minimum documentation.
- Time constraints.