User Acceptance Testing Your R12 Upgrade

2,418 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,418
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
69
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • SDLC V-Model http://www.coleyconsulting.co.uk/testtype.htm
  • SDLC V-Model http://www.coleyconsulting.co.uk/testtype.htm
  • SDLC V-Model http://www.coleyconsulting.co.uk/testtype.htm
  • SDLC V-Model http://www.coleyconsulting.co.uk/testtype.htm
  • Oracle E-Business Suite is an enterprise scale ERP software package with large scale configurability. Excel isn’t. UAT is at the process level, rather than the function. It is about normal business processes.
  • It is generally accepted that the business is responsible for UAT, however - IT can offer guidance around which technical elements of the business process may be impacted by the change.
  • How long could the business go without this working? Is this customer-facing? What is the cost of this not working for an hour? Can this fail silently and, if so, how? Establish which processes are business critical
  • Establish which processes contain the greatest technical risk How long could the business go without this working? Is this customer-facing? What is the cost of this not working for an hour? Can this fail silently and, if so, how?
  • Combine the criticality and technical risk to give each test scenario a weighting Start with the highest risk processes, stop when you run out of time (because you’ll never run out of tests)
  • User Acceptance Testing Your R12 Upgrade

    1. 1. User Acceptance Testing your R12 Upgrade Joanne Nash Vatis Consulting Pty. Ltd. 16 August 2010 The most comprehensive Oracle applications & technology content under one roof
    2. 2. Overview <ul><li>Purpose of UAT </li></ul><ul><li>Who should perform UAT? </li></ul><ul><li>What could we test? </li></ul><ul><li>How do we work out what we should test? </li></ul>
    3. 3. What do I test?
    4. 4. Theory The Business IT
    5. 5. Start with Business Process The upgrade process begins with an update of the business processes to incorporate new and changed functionality
    6. 6. IT deliverables The project team perform the upgrade and complete configuration changes for new functionality
    7. 7. 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
    8. 8. The Big Picture
    9. 9. Who should be responsible for UAT?
    10. 10. The Business Perspective <ul><li>Why is the EBS not like other software? </li></ul><ul><li>I.T. changed it – they should know what to test </li></ul>
    11. 11. The IT Perspective <ul><li>The business owns the system </li></ul><ul><li>Familiarity with the business process </li></ul>
    12. 12. Can We All Agree?
    13. 13. What should we test?
    14. 14. Scenario Criticality <ul><li>How long could we go with this not working? </li></ul><ul><li>How visible is this process – customers, suppliers, reporting </li></ul>
    15. 15. Functional Risk <ul><li>What changed? </li></ul><ul><li>What has failed for others? </li></ul>
    16. 16. Activity – Refer Handout
    17. 17. Test Order
    18. 18. Conclusion <ul><li>1) Scenario Based </li></ul><ul><li>2) High risk first </li></ul>
    19. 19. Questions
    20. 20. Tell us what you think… <ul><li>http://feedback.insync10.com.au </li></ul>

    ×