End users, and more precisely end users involved in acceptance testing decide whether a new application or system will go live or not. Therefore it is very important they are in the same pursuit of quality as the rest of the project. End users are no dedicated testers, although sometimes we expect them to be. Just by looking at their available time for testing, we already know they are not. The fact that they are not trained to be testers, doesn’t make it easier. But are we really looking for dedicated testers here? During this presentation, Erik will explain how you can involve end users in such a way that we optimize their added value during their testing activities. An error often made in projects is that end users are only involved during test execution. It’s by having them participate in the test process on regular, well selected moments that we can get the best out of acceptance testing. By means of a case study, Erik points out these moments. To start with, the acceptance testers need to know the goal of their testing activities. Knowing that, the acceptance testers are already involved at the end of the analysis phase in order to help the writing and prioritisation of high level test scenarios together with setting up the entry criteria for starting the acceptance test phase. Consequently, the acceptance testers will get demos on a regular basis of the software already delivered. These demos deliver valuable information, both for the project team as for the end users. And finally, after having assessed the test readiness of the system through system testing, the end users will execute their test cases closely monitored by the test coordinator. While executing the tests, it is up to the test coordinator to make sure the end users are always updated on the defects. The presentation will provide the audience with practical advice, examples and templates on how to set up their acceptance testing in a flexible way without drowning in administrative tasks.

1. Erik Boelen
qa consult, Belgium
Professional Testing®
Network
Track T4 - EuroSTAR 2011
Acceptance Testing at its best

2. What will I talk about?
Practical acceptance testing
with an added value

3. Business departments
Project team 1 Project team 2
Test coördinator
Acceptance Testers
Who is involved?

4. Who is an acceptance tester?
Decision taker
Knowledge carriers
??
??

5. What do we build?

6. How do we do this?
Analysis Development Testing

7. Where is acceptance testing?
Preparation of TRH Guided demos Continuous guiding
TRH
Validation
Acceptance
Test ready?
GO / NO
GO
System test
Analysis Development Testing

8. We prepare together
Preparation of TRH Guided demos Continuous guiding
TRH
Validation
Test
ready?
GO / NO
GO
System test
Analysis Development Testing

9. We prepare together
It should be possible to….
Priorities
Status
Remarks
Test Requirements Hierarchy

10. We prepare together
• Functional analysis translated
to the application
• Follow the business process
• Test coordinator sets up based
on functional analysis
• Acceptance testers validate,
change & set priorities
TRH Process

11. We prepare together
• (Non) Functional
• Weighted averages
• Absolute figures
• Clear for acceptance testers

12. We prepare together
TRH related acceptance criteria
Acceptance Criteria

13. We prepare together
Immediate involvement
Aware of the content
Less abstract
People start thinking
High priorities

14. Everyone is involved
Preparation of TRH Guided demos Continuous guiding
TRH
Validation
Test
ready?
GO / NO
GO
System test
Analysis Development Testing

15. Guided demos
Small groups
Interactive demo what to do and what NOT to do
All remarks are welcome

16. Guided demos
Demo 1
Based on TRH
‘First look’ assessment
results
All remarks are logged
Demo acceptance criteria
If needed, demo again
Partial versus complete
Demo 2
Demo 3
Demo 4

17. Guided demos
Abstract becomes real
Testers can think of test scenarios
First impressions
Vision provides new insights
Limited demos (at the start)

18. Under close guidance
Preparation of TRH Guided demos Continuous guiding
TRH
Validation
Test
ready?
GO /
NO GO
System test
Analysis Development Testing

19. Under close guidance
• Dedicated testroom
• Test coordinator always
present
• Close contact with developers
• Constant view on TRH
• Instant follow-up
• Prevent frustrations

20. Under close guidance
Continuously kept up to date

21. Under close guidance

22. Under close guidance
Continuously kept up to date

23. Under close guidance
Immediate response
Fast feedback
Less room for interpretation
More room for ventilation
Indepth knowledge of
application required
Good moderation skills needed

24. Conclusion
Continuous involvement…
Continuous integration…
Continuous interaction…
Continuous guidance…
…. gives you great results!

25. Where to find the material?
www.erikboelen.be
Template TRH
Acceptance Criteria
Slides
White Paper

26. Who am I?
Erik Boelen
•Member of Professional Testing Network
•www.professionaltestingnetwork.eu
•Twitter - @destruise
•Email – erik.boelen@me.com
•www.erikboelen.be

27. 27
Questions?