User acceptance testing your r12 upgrade
•Télécharger en tant que PPT, PDF•
2 j'aime•3,675 vues
![Overview ,[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (18)
Similaire à User acceptance testing your r12 upgrade
Similaire à User acceptance testing your r12 upgrade (20)
Plus de InSync Conference
Plus de InSync Conference (20)
Dernier
Dernier (20)
User acceptance testing your r12 upgrade
- 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
- 3. What do I test?
- 4. Theory The Business IT
- 5. Start with Business Process The upgrade process begins with an update of the business processes to incorporate new and changed functionality
- 6. IT deliverables The project team perform the upgrade and complete configuration changes for new functionality
- 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
- 9. Who should be responsible for UAT?
- 12. Can We All Agree?
- 13. What should we test?
- 16. Activity – Refer Handout
- 17. Test Order
- 19. Questions
Notes de l'éditeur
- 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)