What is testing Software testing can be stated as the process of validating and verifying that a software program/application/product: 1.

meets the requirements that guided its design and development; 2. works as expected; and 3. can be implemented with the same characteristics.

Static Testing Vs Dynamic Testing 1. Static testing is a form of software testing where the software isnt actually used. In dynamic testing the software must actually be compiled and run. 2. It is generally not detailed testing, but checks mainly for the sanity of the code, algorithm, or document. It is primarily syntax checking of the code or and manually reading of the code or document to find errors Dynamic analysis refers to the examination of the physical response from the system to variables that are not constant and change with time 3. This type of testing can be used by the developer who wrote the code, in isolation. Code reviews, inspections and walkthroughs are also used. Some of dynamic testing methodologies include unit testing, integration testing, system testing and acceptance testing. 4. This is the verification portion of Verification and Validation Dynamic testing is the validation portion of Verification and Validation. 5. These are verification activities. Code Reviews, inspection and walkthroughs are few of the static testing methodologies. These are the Validation activities. Unit Tests, Integration Tests, System Tests and Acceptance Tests are few of the Dynamic Testing methodologies.

Black box Testing (BBT) Also known as functional testing. Asoftware testing technique whereby the internal workings of the item being tested are not known by the tester. For example, in a black box test on a software design the tester only knows the inputs and what the expected outcomes should be and not how the program arrives at those outputs. The tester does not ever examine the programmingcode and does not need any further knowledge of the program other than its specifications. The advantages of this type of testing include: The test is unbiased because the designer and the tester are independent of each other. The tester does not need knowledge of any specific programming languages. The test is done from the point of view of the user, not the designer. Test cases can be designed as soon as the specifications are complete. The disadvantages of this type of testing include: The test can be redundant if the software designer has already run a test case. The test cases are difficult to design. Testing every possible input stream is unrealistic because it would take a inordinate amount of time; therefore, many program paths will go untested. For a complete software examination, both white box and black box tests are required. White Box Testing Also known as glass box, structural, clear box and open box testing. Asoftware testing technique whereby explicit knowledge of the internal workings of the item being tested are used to select the test data. Unlike black box testing, white box testing uses specific knowledge of programming codeto examine outputs. The test is accurate only if the tester knows what the program is supposed to do. He or she can then see if the program diverges from its intended goal. White box testing does not account for errors caused by omission, and all visible code must also be readable. For a complete software examination, both white box and black box tests are required.

Software verification and validation Software testing is used in association with verification and validation:[20]

Verification: Have we built the software right? (i.e., does it match the specification). Validation: Have we built the right software? (i.e., is this what the customer wants).

The terms verification and validation are commonly used interchangeably in the industry; it is also common to see these two terms incorrectly defined. According to the IEEE Standard Glossary of Software Engineering Terminology: Verification is the process of evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase. Validation is the process of evaluating a system or component during or at the end of the development process to determine whether it satisfies specified requirements.