UPLOAD

    755.9K

    Software Testing

    Published: May 30, 2018

    Software Testing Tip

    Comments

    Software Testing

    • 1. SOFTWARE TESTING SOFTWARE TESTING 1 zamanlayıcı
    • 2. SOFTWARE TESTING Testing is the process of manually or automatically testing and evaluating a system to verify that it meets specified requirements or to determine the difference between expected and observed results. Also ; We can say , The test is an activation to confirm the quality of the software zamanlayıcı SOFTWARE TESTING
    • 3. Defect Lifecycle Defect Lifecycle Incorrect Configuration Incorrect Test Case Error Failure Incident Bug /defect
    • 4. WHAT IS IT BUG / DEFECT ? WHAT IS IT BUG / DEFECT ? Flaw in a component or system that can cause the component or system to fail to perform its function. Document reporting on any flaw in a system that can cause the system to fail to perform its required function. WHAT IS IT BUG / DEFECT ?
    • 5. RISK RISK Factor that could result in future negative consequences; usually expressed as impact. Risk magnitude = effect × probability Risk effect Priority : Business impact Severiyt : System impact RISK
    • 6. Risk Management Process Steps  Risk Management Process Steps 6 Risk Monitoring Risk Control Risk Planning Risk Analysis Risk Identification
    • 7. Product Risk Product Risk :Directly related to the test object. Project Risk : Risk related to management and control of the test project. Risk Analysis : The process of assessing identified risks to estimate their impact and probability of occurrence Product Risk
    • 8. Dynamic Testing Process Dynamic Testing Process System testing Unit testing Regression testing User acceptance testing Integration Testing Stress testing
    • 9. Regression Testing Regression Testing 9 Testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software, as a result of the changes made.
    • 10. Stress Testing Stress Testing 10 Type of performance testing conducted its anticipated or specified workloads, or with reduced availability of resources such as access to memory.
    • 11.  Testing Levels Testing Levels User acceptance Testing System Testing Integration Testing Unit Testing
    • 12. Unit Testing Unit Testing Components of a software are tested. The purpose is to validate that each unit of the software performs as designed.
    • 13. Integration Testing Integration Testing 13 A testing that allows us to test multiple modules working together. The purpose of this level of testing is to expose faults in the interaction between integrated units.
    • 14. System Testing System Testing 14 The process of testing an integrated system to verify that it meets specified requirements. System Testing is the third level of software testing performed after Integration Testing and before User Acceptance Testing.
    • 15. User Acceptance Testing User Acceptance Testing 15 User acceptance testing is the last phase of the software testing. UAT , is one of the final and critical software project procedures that must occur before newly developed software is rolled.
    • 16. White Box Testing White Box Testing White box testing is Software testing method in which the internal structure design implementation of the item being tested is known to the tester. Also we can use ; Clear Box Testing, Open Box Testing, Glass Box Testing, Code-Based Testing or Structural Testing input Output
    • 17. Black Box Testing Black Box Testing Black box testing is a software testing method in which the internal structure/design/implementation of the item being tested is not known to the tester. These tests can be functional or non-functional, though usually functional input Output
    • 18. What is difference ? What is difference ? Functional Keyword driven Security and performance Data driven Internal work logic User viewpoint WHITE BOX TESTING BLACK BOX TESTING
    • 19. Alpha Testing Alpha Testing Alpha testing is a type of acceptance testing; performed to identify all possible bugs before releasing the product to everyday users or public. The focus of this testing is to simulate real users by using blackbox and whitebox techniques. /
    • 20. Beta Testing Beta Testing This Testing of a product is performed by "real users" of the software application Beta version of the software is released to a limited number of end-users of the product to obtain feedback on the product quality. It is the final test before shipping a product to the customers.
    • 21. Maintenance Testing Maintenance Testing Maintenance testing is consisting of two parts First one is, testing the changes that have been made because of the correction in the system of some additional features added to it. The second one is regression tests to prove that the rest of the system has not been affected by the maintenance work.
    • 22. Agile Software Development Agile Software Development 22 Where requirements and solutions evolve through collaboration between self organizing cross functional teams.
    • 23. Accessibility Testing Accessibility Testing A test that measures how easily disabled users can use the software.
    • 24. Usability Testing Usability Testing It is a test type that needs to be done especially for applications where the interface will be used by many users and the interface is important.