Fundamentals OF UAT
Download as PPTX, PDF3 likes1,617 views
User Acceptance Testing (UAT) is a formal testing process used to determine if a system satisfies the needs of end users and business processes. UAT takes place late in the development cycle and involves key stakeholders performing real-world tests using real data. The goals of UAT are to ensure a system's functionality and performance meet requirements before it goes live. Challenges of UAT include environment setup, handling new requirements, and communication. Proper planning, engaged users, and addressing issues early are keys to successful UAT.
Fundamentals OF UAT
- 2. Overview • Introduction to UAT • What is UAT ? • The goal of UAT • Where does UAT fit in ? • Why is UAT so important ? • 7 Challenges of UAT • Traits of a good UAT Tester • Benefits of UAT • Keys to successful UAT • Question
- 3. Introduction Too often software products delivered to the businesses does not meet the user's expectations, especially with regard to the quality and usability of the product. An effective Acceptance Testing process addresses these issues by confirming the functionality and performance of the product prior to its release to the business.
- 4. What is Acceptance Testing ? This is a Formal testing with respect to User needs, Requirements, and Business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system. Wikipedia
- 5. What is Acceptance Testing ? This is a Formal testing with respect to User needs, Requirements, and Business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system. Wikipedia
- 6. User Acceptance Testing: A process of verifying that a solution works for the user.
- 7. The Goal of User Acceptance Testing Requirements System UAT Test Implements • Given business requirements, we build systems that implement the requirements. • UAT are derived from these requirements. • UAT confirms we have confidence that the system satisfies the requirements.
- 8. Where does UAT fit in ? Initiation Requirements Analysis Design Coding Testing Production 1 2 3 4 5 6 Where is the work for UAT performed in this Software Development Lifecycle? • The work associated with UAT begins while requirements are written and continues through the final stage of testing before the client/user accepts the new system The work for User Acceptance Testing is performed here
- 9. Why is UAT Important? • Loss of money – This can include losing customers right due to financial penalties for non-compliance to legal requirements. • Loss of time – This can be caused by transactions taking a long time to process but can include staff not being able to work due to a fault or failure. • Damage to business reputation – If an organization is unable to provide service to their customers due to software problems then the customers will lose confidence or faith in this organization (and probably take their business elsewhere) It is important to test the system to ensure it is error free and that it supports the business that depends on it. The later problems are discovered the more costly they are to fix.
- 10. Types Of Acceptance Testing • Alpha & Beta Testing • Contract Acceptance testing • Regulations Accepting Testing • Functional Testing • Operational Acceptance testing • Performance Testing
- 11. Alpha & Beta Testing • Alpha testing is a type of acceptance testing; perform ed to identify all possible issues/bugs before releasin g the product to everyday users or public • Beta Testing of a product is performed by "real users " of the software application in a "real environment" and can be considered as a form of external user acc eptance testing
- 12. Contract Acceptance testing • Contract Acceptance Testing means that a developed soft ware is tested against certain criteria and specifications w hich are predefined and agreed upon in a contract. The rel evant criteria and specifications for acceptance must be d efined when the contract itself is defined and agreed upon.
- 13. Regulations Accepting Testing • Regulation Acceptance Testing, also known as Compliance Acceptance Testing, examines whether the software compl ies with the regulations. This includes governmental and le gal regulations
- 14. Functional Testing • Functional Testing is a testing technique that is used to te st the features/functionality of the system or Software, sh ould cover all the scenarios including failure paths and bou ndary cases
- 15. Operational Acceptance testing • Also known as Operational Readiness Testing or Productio n Acceptance Testing, these test cases ensure there are workflows in place to allow the software or system to be u sed. This should include workflows for backup plans, user traini ng, and various maintenance processes and security check
- 16. Performance Testing • Performance Testing is a type of software testing that inte nds to determine how a system performs in terms of respo nsiveness and stability under a certain load.
- 17. Challenges of UAT It doesn’t matter if you are part of a billion dollar release o r a startup team, you should overcome these UAT challenges for delivering successful software for the end user.
- 18. Challenges of UAT • UAT Test Planning • UAT environment setup and deployment process • Handling new business requirements as incidents/defects • Unskilled testers or testers without business knowledge • Improper Communication channel • Asking functional test team to perform UAT • The blame game
- 19. Traits Of a Good UAT Tester
- 20. • Experience of user operations. • Not involved in the overall IT project. • Experience in the use of IT facilities. • Respected as an independent thinker. Background
- 21. Skill • Expects the system to fail. • Good communicator. • Avoids politics. • Fence sitter. • Break the system. • Detail oriented .
- 22. Independence • Not involved in user specifications. • Has an independent reporting structure. • Self starter.
- 23. Attitude • Lateral thinker • Optimistic/pessimistic thinker • Tenacious • Analytical
- 24. Tasks of a UAT Teste r
- 25. • Review business requirements and understand their relationship to business needs Analyze Business Requirements • Describe UAT scenarios that will be used to verify the system meets the business requirements Identify UAT Scenarios • Identify the test scenarios, sequence, high-level data, and approach to conduct the UAT Define the Test Plan • Document the steps (i.e., actions), specific data, and expected results for each test Create Test Cases • Execute the test cases and document the outcome of the testsRun the Tests • Document any problems encountered during the testsRecord the Results • Sign-off each test verifying the system meets the stated acceptance criteria Confirm Business Objectives are Met 1 2 3 4 5 7 6
- 26. Benefits of UAT
- 27. • To Satisfy customer / Client. • To uncover hidden requirements. • Getting higher quality products with less expenses. • Stakeholders has a better chance of getting what they paid for. • Test the system with real world scenarios and data. • Find defects earlier, instead of later. • Confirms the system meets the needs of the business. • Provides the business with hands-on demonstration prior to acceptance. Benefits of UAT
- 29. • Base the test on real-world conditions, not user requirements. • Understand Your Users. • Involve your users. • Plan test in advance. • Match your test to users. • Review your test plans and tools Keys To Successful UAT
- 30. Conclusion User Acceptance Testing done well will engage those responsible very early on in the project development cycle. I believe that these UAT guidelines will certainly help us execute a successful UAT plan by overcoming various challenges. Proper planning, communication, execution and motivated UAT team are the keys to successful user acceptance testing.
- 32. Thanks Thanks you all for your time
Editor's Notes
- #10: Most of us have had an experience with software that did not work as expected. Software that doesn’t work can have a large impact on an organization, and it can lead to many problems including:
- #18: UAT test plan (template) should be prepared and communicated to team well before beginning UAT. This will help them for test planning, writing test cases and test scripts and creating UAT environment.
- #19: UAT test plan (template) should be prepared and communicated to team well before beginning UAT. This will help them for test planning, writing test cases and test scripts and creating UAT environment.