Please enable JavaScript.
Coggle requires JavaScript to display documents.
Testing Strategies and Techniques (Types of Acceptance Testing…
Testing Strategies and Techniques
Types of Acceptance Testing
User Acceptance Testing
Verify the system is fit for the use by the business users
Operational Acceptance Testing
Acceptance of thee system by system administrators
Disaster recovery
User management
Maintenance task
Contract Acceptance Testing
Where software has been developed by a third party, ensure it meets acceptance criteria defined in the contract
Regulation Acceptance Testing
Check the system complies with government, legal, safety and other regulations
Alpha and Beta Testing
Applies to the developers of COTS software
Get feedback from potential or existing customers before commercial sale
Functional Testing
Tests WHAT the system does
Considers the external behaviour of the software - Black Box
Occurs at all test levels
Functional Testing includes security and interoperability testing
Non-Functional Testing
Tests HOW the system works
Again considers the external behaviour of the software - Black Box
Measures the characteristics of software that can be quantified on a varying scale
May be performed at all test levels
Structural Testing
Based on knowledge of internal structure- White box
Tests are designed to measured coverage of a particular structure
Coverage measurement applies at all test levels
Component testing
Component integration testing
Acceptance testing
Usually follows specification-based tests
Regression Testing
Checks that amendments to software or environment have no adverse effect on unmodified part of the system
May be performed at all test levels and types
Estimated that 20% to 50% of system changes introduce new defects
Regression testing should take place at all stages of testing after a functional change or fix
Test Plan Entry Criteria
Define when to start testing at the beginning of a test level
Typical entry criteria might include:
Test environment available and ready
Test tool configured in the test eenvironment
Testable code available
Third-party software delivered and software licences bought
Test Plan Exit Criteria
Define when to stop testing at the end of a test level
Typical exit criteria might include:
Measures of testing thoroughness
Cost
Estimates of defect density or reliability
Schedules such as those based on time to market
Test Plan Approaches
The implementation of the test strategy for a specific project
Defined in test plans and refined in test designs
Based on test objectives and risk
Starting point
Test planning
Selecting test design techniques and test types
Defining entry and exit criteria
Approaches may be
Preventative
Reactive