SYSTEM TESTING PPT Prepared by, L.Eshwar QA Engineer
System Testing  System testing is defined as testing the behavior of a system/software as per software requirement specification  Testing the fully integrated applications including external peripherals in order to check how components interact with one another  System testing enables us to test, Verify and validate both the business requirements as well as the applications architecture  The application is tested thoroughly to verify that it meets the technical and functional specifications
Why system testing is required  It is the first level of software testing where the application is tested as a whole  It is done to verify, validate the functional, non functional, business, technical requirements of the software  It also includes the verification and validation of software application architecture
Entry criteria for system testing      Complete software system should be developed Unit testing must be completed Integration testing must be completed Specifications for the product have been completed Test scripts and schedules are ready
Exit criteria for system testing     Application meets all the document requirements and functionalities Defects found during system testing should be fixed and closed All the test cases for the system should be executed No critical defects should be opened
Types of system testing  I. II. III. IV. V. VI. VII. There are more than 50 types in system testing. The mainly using types are Usability testing Stress testing Regression testing Functional testing Load testing Sanity testing & Security testing
How to write system test cases  I. II. The system test cases are written in a similar way as we write in functional test cases. while creating system test cases we have to follow two points System test cases must cover the use cases and scenarios Must validate all types of requirements-UI, Functional, Technical, Non functional, Performance etc..
System testing vs. Integration testing System Testing Integration Testing 1. From requirement specification 1. From interface specification 2. No visibility of code 2. Visibility of integration structure 3.It is a high level testing 3. It is a low level testing 4. The complete system is configured in a controlled environment 4. Test cases are developed with the express purpose of exercising the interface between components
System testing ppt
System testing ppt

System testing ppt

  • 1.
    SYSTEM TESTING PPT Preparedby, L.Eshwar QA Engineer
  • 2.
    System Testing  System testingis defined as testing the behavior of a system/software as per software requirement specification  Testing the fully integrated applications including external peripherals in order to check how components interact with one another  System testing enables us to test, Verify and validate both the business requirements as well as the applications architecture  The application is tested thoroughly to verify that it meets the technical and functional specifications
  • 3.
    Why system testingis required  It is the first level of software testing where the application is tested as a whole  It is done to verify, validate the functional, non functional, business, technical requirements of the software  It also includes the verification and validation of software application architecture
  • 4.
    Entry criteria forsystem testing      Complete software system should be developed Unit testing must be completed Integration testing must be completed Specifications for the product have been completed Test scripts and schedules are ready
  • 5.
    Exit criteria forsystem testing     Application meets all the document requirements and functionalities Defects found during system testing should be fixed and closed All the test cases for the system should be executed No critical defects should be opened
  • 6.
    Types of systemtesting  I. II. III. IV. V. VI. VII. There are more than 50 types in system testing. The mainly using types are Usability testing Stress testing Regression testing Functional testing Load testing Sanity testing & Security testing
  • 7.
    How to writesystem test cases  I. II. The system test cases are written in a similar way as we write in functional test cases. while creating system test cases we have to follow two points System test cases must cover the use cases and scenarios Must validate all types of requirements-UI, Functional, Technical, Non functional, Performance etc..
  • 8.
    System testing vs.Integration testing System Testing Integration Testing 1. From requirement specification 1. From interface specification 2. No visibility of code 2. Visibility of integration structure 3.It is a high level testing 3. It is a low level testing 4. The complete system is configured in a controlled environment 4. Test cases are developed with the express purpose of exercising the interface between components