{"id":1527,"date":"2018-09-03T14:41:14","date_gmt":"2018-09-03T14:41:14","guid":{"rendered":"https:\/\/www.h2kinfosys.com\/blog\/?p=1527"},"modified":"2021-11-03T18:05:29","modified_gmt":"2021-11-03T12:35:29","slug":"acceptance-testing","status":"publish","type":"post","link":"https:\/\/www.h2kinfosys.com\/blog\/acceptance-testing\/","title":{"rendered":"ACCEPTANCE TESTING"},"content":{"rendered":"<p>The acceptance testing of software application is an important software testing level. The <a href=\"https:\/\/www.h2kinfosys.com\/blog\/basics-software-testing\/\">software testing<\/a> is conducted at the different levels of software development by the different members of the IT project team and stakeholders. At each level, the test objective is different. The different levels of software testing are: unit or component testing, integration testing, system testing and acceptance testing.<\/p>\n<p><b> <\/b>The <a href=\"https:\/\/www.h2kinfosys.com\/blog\/build-acceptance-testing\/\">acceptance testing<\/a> is a type of formal testing conducted to determine its acceptance criteria. There are various types of acceptance testing:<\/p>\n<ul>\n<li>user acceptance testing<\/li>\n<li>operational acceptance testing<\/li>\n<li>contractual and regulatory acceptance testing<\/li>\n<li>business acceptance testing<\/li>\n<\/ul>\n<h2>User acceptance testing:<\/h2>\n<p>User acceptance testing is performed by the intended users of the software to check if the system meets their expectations. the user friendliness and completeness of the software application is tested. UAT can be either alpha testing or beta testing. It is also called as application testing or end-user testing.<\/p>\n<h2>Operational acceptance testing:<\/h2>\n<p>Operation acceptance testing is performed by the system administrators to ensure the system works properly in the operational environment of the client.<\/p>\n<h2>Contractual and regulatory acceptance testing:<\/h2>\n<p>Contractual acceptance testing is performed by the users and software testers to ensure the software meets the contractual requirements of the client.<\/p>\n<p>Regulatory acceptance testing is performed by users and software testers to ensure the software is compliant with government, legal or safety standards.<\/p>\n<h2>Business acceptance testing:<\/h2>\n<p>Business acceptance testing is performed within the development organisation by the vendor to guarantee that the system will eventually pass the User acceptance testing.<\/p>\n<p>The software applications are subjected to various levels of acceptance testing to build the confidence of the <a href=\"https:\/\/www.h2kinfosys.com\/blog\/different-roles-software-testing-team\/\">IT team<\/a> and stakeholders, in the system.<\/p>\n<p><span style=\"font-weight: 400;\">Acceptance testing is also called as formal testing with respect to the user needs and requirements and business processes conducted to decide whether or not the system satisfies the acceptance criteria. Acceptance testing enables the user, customers or other authorised entity to decide whether to accept or to not accept the system.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Acceptance testing uses the black box testing technique and is executed manually. Acceptance testing is done after system testing and also before making the system available in production for actual use.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Types of acceptance testing are:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Internal acceptance testing- which can be called as alpha testing is performed by members of the organisation, that developed the software but who cannot be directly involved in the project.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">External acceptance testing- This type of testing is done by people who wouldn\u2019t be the staff of the organisation that developed the software.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Customer acceptance testing- this type of acceptance testing is done by the customers of the organisation that developed the software. They are ones who asked the organisation to develop the software.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">User acceptance testing- this type of testing is also called as beta testing which is performed by the customers or end users.<\/span><\/li>\n<\/ol>\n<p><img decoding=\"async\" src=\"https:\/\/lh5.googleusercontent.com\/iOkVpSeKXJ6c8C11gf1RPu97uXwtUaQJvHfLnlxY7zDJz0n0HRcGYq53Be2Tu7grE-q9e2Y6GY-GcrcCqCk8unzrgdoetvAl7_9-ZB2hgrugVjGyW4HowFT-obGEHEum1GKCEVc\" alt=\"Acceptance Testing\" width=\"604.8268003463745\" height=\"302.62540876865387\" title=\"\"><\/p>\n<p><span style=\"font-weight: 400;\">Use of acceptance testing<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To find the defects missed during the functional testing phase.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">How well the product will be developed.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A product is what actually the customers need.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A feedback helps in improving the product performance and user experience.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Minimise the issues arising from production.<\/span><\/li>\n<\/ol>\n<h2><b>Steps to perform acceptance testing:<\/b><\/h2>\n<p><b>Requirement analysis<\/b><span style=\"font-weight: 400;\">&#8211; the testing team analyses requirement document to find the out the of purpose of the developed software. Test planning is done using requirement document, process flow diagrams, system requirement specification etc.<\/span><\/p>\n<p><b>Test plan creation<\/b><span style=\"font-weight: 400;\">&#8211; test creation outlines the complete strategy of the testing process. This strategy is used to make sure and verify whether the software is conforming specified requirements or not.<\/span><\/p>\n<p><b>Test case Designing<\/b><span style=\"font-weight: 400;\">&#8211; This step has execution of test cases by using appropriate input values. This testing team gathers input value from the end user then all test cases are executed by both tester and end user to make sure the software is working correctly or not.<\/span><\/p>\n<h2><b>How to start user acceptance testing?<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">User acceptance testing is necessarily done at the end of the software development life cycle. That means that the developed software must be largely feature complete.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The project team defines a UAT plan right at the beginning of a project; it executes the UAT test cases.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Let us consider the example, as we got recruited by some abc company to do the UAT testing. They had a development team approached us to check if the developed archiving feature actually works for the user.<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>UAT scope- <\/b><span style=\"font-weight: 400;\">as we are in charge to test the newly developed archive feature of the software, we define the series of features we want to test. As we can see the test example focuses on the desktop tests only while the mobile tests are not included.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UAT assumptions and constraints<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">For the test suite example of testing archiving feature on the desktop, constraints are often the OS to be used and specific browser versions and that we must clearly state the assumptions like how the tester handles the error reporting.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">3. UAT risks<\/span><\/p>\n<p><img fetchpriority=\"high\" decoding=\"async\" src=\"https:\/\/lh4.googleusercontent.com\/RMPqT7td7e8RQJdR3ef9tfp0pb2LNGRjKjVIbOHWjZLIUaAweZ-fba3fbOd0u1C0ynfhGRMlXl1gVTHPAut5wiokS12GBmPBMXqfhuHV7GvrAosEB6_7iXzU04KwgAhu5L1eKI4\" alt=\"UAT test case example: UAT risks planning\" width=\"457\" height=\"272\" title=\"\"><\/p>\n<p><span style=\"font-weight: 400;\">In our example we can face some risks during the UAT<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Not properly trained UAT testers, incomplete UAT environment, error handling, UAT test failure.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">4.UAT team roles and responsibilities<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The UAT team will assure<\/span><\/p>\n<p><span style=\"font-weight: 400;\">That defined test cases are planned and conducted accordingly. The test results are documented and shared among the project team.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">5.UAT entry criteria<\/span><\/p>\n<p><span style=\"font-weight: 400;\">To start the UAT, archiving feature the following must be the criteria.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The development of the archive feature is fully completed. All reported bugs are fixed. The UAT test environment is available and testers are trained to start the UAT test<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">the development of the archive feature in abc software is completed<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">integration tests are completed<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">no high or medium defects are reported<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">all reported bugs should be fixed<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UAT test environment(hardware, software, location) is ready<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">testers got briefed and ready to start testing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UAT test plan is available<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">6. UAT requirement- based test cases<\/span><\/p>\n<p><span style=\"font-weight: 400;\">As the user acceptance looks to verify if the business and user requirements are met, test case procedure could look like<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">please visit: abc.com<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">log in with the following credentials<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">\u00a0username: nancy<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u00a0 password: 123<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">open available abc board<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">archive the first card on board.<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">Expected results<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The card will be removed<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The card will be moved to archive.<\/span><\/p>\n<h2><b>Check your understanding:<\/b><\/h2>\n<ol>\n<li>List the different types of acceptance testing listed in above article.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>The acceptance testing of software application is an important software testing level. The software testing is conducted at the different levels of software development by the different members of the IT project team and stakeholders. At each level, the test objective is different. The different levels of software testing are: unit or component testing, integration [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":10296,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[193,294,292,291,293,113],"class_list":["post-1527","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-qa-tutorials","tag-acceptance-testing","tag-business-acceptance-testing","tag-contractual-acceptance-testing","tag-operational-acceptance-testing","tag-regulatory-acceptance-testing","tag-user-acceptance-testing"],"_links":{"self":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/1527","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/comments?post=1527"}],"version-history":[{"count":0,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/1527\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media\/10296"}],"wp:attachment":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media?parent=1527"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/categories?post=1527"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/tags?post=1527"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}