Presentation Description

BCA 5th sem


Presentation Transcript



Slide 2:

Testing The execution of a program to find its faults. Verification The process of proving the programs correctness. Validation The process of finding errors by executing the program in a real environment Debugging Diagnosing the error and correct it Testing is a process of executing a software application with the intent of finding errors and to verify that is satisfies specified requirements

Top-down Integration Test:

Top-down Integration Test The control program is tested first. Modules are integrated one at a time. Emphasize on interface testing Advantages : No test drivers needed Interface errors are discovered early Modular features aid debugging Disadvantages : Test stubs are needed Errors in critical modules at low levels are found late.

Bottom-up Integration Test:

Bottom-up Integration Test Allow early testing aimed at proving feasibility Emphasize on module functionality and performance Advantages : No test stubs are needed Errors in critical modules are found early Disadvantages : Test drivers are needed Interface errors are discovered late

Black Box Testing:

Black Box Testing Checks that the product conforms to specifications Cannot determine how much code has been tested Program Omissions detected by black-box tests

White Box Testing:

White Box Testing Allows tester to be sure every statement has been tested. Difficult to discover missing functionality. Commissions detected by White-box tests Program

Alpha and Beta Testing:

Alpha and Beta Testing It’s best to provide customers with an outline of the things that you would like them to focus on and specific test scenarios for them to execute. Provide with customers who are actively involved with a commitment to fix defects that they discover.

Acceptance Testing:

Acceptance Testing Similar to validation testing except that customers are present or directly involved. Usually the tests are developed by the customer THANK YOU