Browse Article

User Acceptance Testing And It’s Effective Execution

July 8, 2016 | Author: | Posted in Careers

User Acceptance Testing And It’s Effective Execution . CRB Tech would assure you best software testing training in Pune.

Let us begin this blog with the definition of UAT or User Acceptance Testing.


User Acceptance testing (UAT) is the last stage of the software testing process or the test planning process. Amidst UAT, real software users test the product to ensure it can deal with required tasks in real situations, as indicated by specifications.

Give us a chance to put this idea to test. UAT resembles User Acceptance Testing. We comprehend what testing is, acceptance implies agreement or approval. Client with regards to a software product is either the buyer of the product or the individual who asked for it to be developed for him/her (customer).

Stakeholders who perform UAT:

Clients or customer — This could be it is possible that somebody who is purchasing a product(on account of commercial software) or somebody who has had a software custom worked through a service provider and supplier or the end client if the product is made accessible to them early and when their feedback is looked for.

When is it performed?

This is ordinarily the last stage before the software application or the product goes live or before the conveyance of the product is acknowledged. UAT is after the item itself is altogether tried (i.e after system testing).

UAT Planning:

The procedure is nearly the same as with the regular test plan for the system stage. The most widely recognized methodology followed in a large portion of the projects is to get ready for both system and UAT testing stages together. For more info. on UAT test plan and an example, look at the joined test plan report’s UAT areas.

The dates, environment, actors(who), communication conventions, parts and obligations, formats, results and their analysis procedure, entry-exit criteria — every one of this and whatever else applicable will be found in the UAT test plan. Whether the QA team is partaking, mostly taking an interest or not taking an interest at all in the UAT, we must plan this stage and ensure everything is contemplated.

Design Phase:

In view of the criteria, we (QA team) give them the clients a rundown of UAT test cases. UAT test cases are not unique in relation to our regular system test cases. They are only a sub set since we test the majority of the application rather than simply the key functional areas. It may include both functional and non-functional testing.

Notwithstanding these, the information, formats to record test results, administrative strategies, defect filing mechanism must be set up before we move to the following stage.

Execution Phase:

More often than not, whenever feasible, UAT happens in a meeting or war room kind of a set up where the clients, PM, QA team delegates all sit together for a day or two and work our work through all the acceptance test cases.

Alternately if there should be an occurrence of QA team executing the tests, we run them on the AUT.

When every one of the tests are run and the outcomes are in hand, the Acceptance Decision is made. This is likewise called the Go/No-Go choice all the more conversationally. In the event that the clients are fulfilled it’s a Go, or it’s a No-go.

UAT execution can be done via manual testing or automation testing techniques.

Important Points:

  1. UAT is not about the fields, buttons or pages . The hidden suspicion before even the UAT starts is that, all that fundamental stuff is tried and is working fine. God restrict, the users discover a bug as fundamental as that — it is terrible news for the QA team.
  2. UAT is likewise a type of testing at its center which implies there is a decent risk of distinguishing a few bugs at this stage as well. It in some cases happens. Beside the way that it is a noteworthy escalation on the QA team, the UAT bugs generally implies a meeting to sit and examine how to handle them since taking after UAT there is normally no opportunity to alter and retest.
  3. UAT is named Alpha and Beta testing, yet that classification is not all that essential with regards to common software development projects in a service based industry.

Hope this blog on UAT will prove to be fruitful to you. CRB Tech would be glad to assist you in getting a software testing job in Pune.

More Related Blog:

How Do Test Cases Differ From Test Scenarios?

Difference Between Monkey Testing And Gorilla Testing

Article Source


this is training and placement institute in pune .

This author has published 44 articles so far.