Upload
insync-conference
View
1.751
Download
2
Tags:
Embed Size (px)
Citation preview
User Acceptance Testing your R12 Upgrade
Joanne NashVatis Consulting Pty. Ltd.
16 August 2010
The most comprehensive Oracle applications & technology content under one roof
Overview
• Purpose of UAT
• Who should perform UAT?
• What could we test?
• How do we work out what we should test?
What do I test?
Theory
The BusinessThe Business
ITIT
Start with Business Process
The upgrade process begins with an update of the business processes to incorporate new and changed functionality
IT deliverables
The project team perform the upgrade and complete configuration changes for new functionality
Testing
Unit testing for customisations
Interface testing establishes whether any interfaces are affected by the upgrade.
System Testing (aka Functional Testing) tests the application functionality
UAT - must be based on business process
The Big Picture
Who should be responsible for UAT?
The Business Perspective
• Why is the EBS not like other software?
• I.T. changed it – they should know what to test
The IT Perspective
• The business owns the system
• Familiarity with the business process
Can We All Agree?
What should we test?
Scenario Criticality
• How long could we go with this not working?
• How visible is this process – customers, suppliers, reporting
Functional Risk
• What changed?• What has failed for
others?
Activity – Refer Handout
Test Order
Conclusion1) Scenario Based 2) High risk first
Questions
Tell us what you think…
• http://feedback.insync10.com.au