Software Test Plan

Software Test Plan: The test plan document typically contains the strategic approach to testing a system (software). Planning is very important in everyone's life, similarly for testing the software also.



 There are also other IEEE documents that suggest what should be contained in a test plan:

• 829-1983 IEEE Standard for Software Test Documentation (superseded by 829-1998)^[2]
• 829-1998 IEEE Standard for Software Test Documentation (superseded by 829-2008)^[3]
• 1008-1987 IEEE Standard for Software Unit Testing^[4]
• 1012-2004 IEEE Standard for Software Verification & Validation Plans^[5]
• 1059-1993 IEEE Guide for Software Verification & Validation Plans (withdrawn)^[6]

White Box Testing

White Box Testing – Testing the functionality of the application by considering the internal logic of the application. It is also know as Glass Box Testing.

Black Box Testing

Black Box Testing – Testing the functionality of the application without considering the internal logic of the application.

Types of software Testing

Software Testing Types:


Black Box Testing – Testing the functionality of the application without considering the internal logic of the application.




White Box Testing – Testing the functionality of the application by considering the internal logic of the application. It is also know as Glass Box Testing.




End-To-End Testing - Testing refers to User Level testing of Component based systems. It verifies that the integrated component functions correctly as part of the overall system and the existing Components of the System work as before. End-To-End Testing approaches the system from a Functional Side and the Architecture side thus combining Black-Box and White-Box Techniques. The Steps required to perform End-To-End testing include Test Design Test Execution and Test Results Analysis