2.2.

4 ACCEPTANCE TESTING
What is acceptance testing?

• Is final stage of validation

- Related to user needs, requirements, business processes
- User should perform or be closely involved
- Final user sign-off

• How to approach
- Use mixture of scripted and unscripted testing
- Use Model Office concept
Why user should involve

• User would know:

- What really happens in business situations
- Complexity of business relationships
- How to do their work by using the system
- Variants to standard tasks
- Example for real cases
- How to identify sensible workarounds

•  User could understand details about the new system

 Acceptance testing

80% of function
by 20% of code
• 20% of function
• by 80% of code
System testing
Contract acceptance testing
• Contract to supply a software system
- agreed at contract definition stage
- acceptance criteria defined and agreed
- may not have kept up to date with changes
• Contract acceptance testing is against the contract and any
documented agreed changes
- not what the users wish they had asked for
- this system, not wish system
Alpha and Beta test: similarities

• Testing by users, pre order or representatives of your market

• When software is stable
• Use the product in a realistic way in its operational environment
• Give comments back on the product
- Faults found
- experiences expected
- Improvement/ enhancement suggest?
Alpha and beta test: differences
• Alpha test
- This test takes place at the developer's site
- Developers observe the users and note problems
• Beta test
- sends the system to a cross-section of users who install it and
use it under real-world working conditions
- The users send records of incidents with the system to the
development organization where the defects are repaired.