SlideShare a Scribd company logo

S.t.

•Download as PPTX, PDF•
•
P
Prashant Gupta

Software testing is the process of identifying errors, completeness, and quality of software. It involves executing programs under different conditions through manual or automated means to uncover as many errors as possible. The goal is to demonstrate that the software meets requirements specifications with minimum cost and effort. There are different types of testing like unit, integration, and system testing that occur at various stages of the software development life cycle. Test cases are specific procedures used to test requirements and include identification of what is being tested, success and failure criteria, test steps, and test data.

1 of 13
Presented by Prashant gupta B.Tech. (CS) 1310303038
It is the process used to identify the correctness, completeness and quality of developed computer software. It is the process of executing a program under positive and negative conditions by manual or automated means. It checks for the :-  Specification  Functionality  Performance
Uncover as many as errors (or bugs) as possible in a given product. Demonstrate a given software product matching its requirement specifications. Validate the quality of a software testing using the minimum cost and efforts. Generate high quality test cases, perform effective tests, and issue correct and helpful problem reports.
Error : It is a human action that produces the incorrect result that produces a fault. Bug : The presence of error at the time of execution of the software. Fault : State of software caused by an error. Failure : Deviation of the software from its expected result. It is an event.
Project Initiation System Study Summary Reports Analysis Regression Test Report Defects Execute Test Cases ( manual /automated ) Design Test Cases Test Plan Testing Life Cycle
Test Case It is a specific procedure of testing a particular requirement. It will include: Identification of specific requirement tested Test case success/failure criteria Specific steps to execute test Test data
Black box testing  No knowledge of internal program design or code required.  Tests are based on requirements and functionality. White box testing  Knowledge of the internal program design and code required.  Tests are based on coverage of code statements, branches, paths and conditions. Testing Methodologies
Testing Levels  UNIT TESTING  INTEGRATION TESTING  SYSTEM TESTING
UNIT TESTING Tests each module individually. Follows a white box testing (Logic of the program). Done by developers.
Once all the modules have been unit tested, integration testing is performed. It is systematic testing. Produce tests to identify errors associated with interfacing. Types: 1. Big Bang Integration testing 2. Top Down Integration testing 3. Bottom Up Integration testing 4. Mixed Integration testing
 The system as a whole is tested to uncover requirement errors.  Verifies that all system elements work properly and that overall system function and performance has been achieved. Types: 1. Alpha Testing 2. Beta Testing 3. Acceptance Testing 4. Performance Testing
Alpha Testing It is carried out by the test team within the developing organization. Beta Testing It is performed by a selected group of friendly customers. Acceptance Testing It is performed by the customer to determine whether to accept or reject the delivery of the system. Performance Testing It is carried out to check whether the system meets the nonfunctional requirements identified in the SRS document.
S.t.

More Related Content

S.t.

  • 2. It is the process used to identify the correctness, completeness and quality of developed computer software. It is the process of executing a program under positive and negative conditions by manual or automated means. It checks for the :-  Specification  Functionality  Performance
  • 3. Uncover as many as errors (or bugs) as possible in a given product. Demonstrate a given software product matching its requirement specifications. Validate the quality of a software testing using the minimum cost and efforts. Generate high quality test cases, perform effective tests, and issue correct and helpful problem reports.
  • 4. Error : It is a human action that produces the incorrect result that produces a fault. Bug : The presence of error at the time of execution of the software. Fault : State of software caused by an error. Failure : Deviation of the software from its expected result. It is an event.
  • 5. Project Initiation System Study Summary Reports Analysis Regression Test Report Defects Execute Test Cases ( manual /automated ) Design Test Cases Test Plan Testing Life Cycle
  • 6. Test Case It is a specific procedure of testing a particular requirement. It will include: Identification of specific requirement tested Test case success/failure criteria Specific steps to execute test Test data
  • 7. Black box testing  No knowledge of internal program design or code required.  Tests are based on requirements and functionality. White box testing  Knowledge of the internal program design and code required.  Tests are based on coverage of code statements, branches, paths and conditions. Testing Methodologies
  • 8. Testing Levels  UNIT TESTING  INTEGRATION TESTING  SYSTEM TESTING
  • 9. UNIT TESTING Tests each module individually. Follows a white box testing (Logic of the program). Done by developers.
  • 10. Once all the modules have been unit tested, integration testing is performed. It is systematic testing. Produce tests to identify errors associated with interfacing. Types: 1. Big Bang Integration testing 2. Top Down Integration testing 3. Bottom Up Integration testing 4. Mixed Integration testing
  • 11.  The system as a whole is tested to uncover requirement errors.  Verifies that all system elements work properly and that overall system function and performance has been achieved. Types: 1. Alpha Testing 2. Beta Testing 3. Acceptance Testing 4. Performance Testing
  • 12. Alpha Testing It is carried out by the test team within the developing organization. Beta Testing It is performed by a selected group of friendly customers. Acceptance Testing It is performed by the customer to determine whether to accept or reject the delivery of the system. Performance Testing It is carried out to check whether the system meets the nonfunctional requirements identified in the SRS document.