as the name "user acceptance testing" tell us that it is
related to clients/user ,who use our software /application ,
or whatever we deliver them called as product. we provide
them -their requirements ,use cases, test cases and their
result so that they will be ease of running that product. 
if in UAT any bug related to functionality the status of that
bug will be major.

A formal product evaluation performed by a customer as a 
condition of purchase. The testing can be based upon the 
User Requirements Specification to which the system should 
conform. Use Acceptance testing is black box testing. 

User Acceptance Testing is the last stage of the Software 
Development Lifecycle. User acceptance testing we 
validating all the user requirements specified in SRS is 
met after code freeze. The acceptance test is the 
responsibility of the client/customer or project manager; 
however, it is conducted with the full support of the 
project team. Before the software goes live determining if 
software is satisfactory to an end-user or customer. 
The  status of the bug would  depends on the bug found .but 
priority would be given high.

1.User Acceptance Testing is To check the 
Product/Application satisfies the User/Client.

2.User Acceptance Testing is done by Client/user.

3. Priority is High.

   Severity depends How For the Application is Affected.

User Acceptance testing is nothing but after completion of 
all possible functional and system tests, the project 
management team invite the users to collect feed back of 
the customer site people this type of testing is called the 
user acceptance testing.

Under acceptance testing project management team fallow the 
some tests.
	They are,
c)	Alpha testing.
d)	Beta testing
e)	Port testing

	If you got any defect while doing UAT then if I can 
possible then I will solve or I take the my lead or Pm 
suggestion

	After I will explain the defect to client the 
defect client give suggestion the I will give to the 
severity and priority.

user acceptance testing 2 types 
alpha and beta

alpha testing is done in company by test engineers before 
delivering the software in to client site  this is done by 
test engineer

User acceptance Testing
User acceptance testing  is done by clients by clients 
place.
It build confidence to client
It is real time data
Mostly Black Box Testing

It would be most important to complete the user acceptance
testing so as to ensure that the system, which is to be
implemented is working correctly. The completion of the user
manuals is similar to the performance of code reviews. If
time is tight, the last thing one would want to do is add
another enhancement. It would be necessary to freeze the
code and complete the testing, then make any other changes
as future enhancements. It would be appropriate to have the
code documented and reviewed, but unless the acceptance
testing is completed, there is no guarantee that the system
will work correctly and meet user requirements.

Validates that the right system was built.

It is a kind of alpha testing, done by the developing 
organization.....when the product is not completed by the 
given time or "Time exceeds the deadline time".

User Acceptance Testing :
This type of testing is done by the Cust / Client or a 
testing team from the clients side.

The appln here is tested for all its features as an end 
user.

User acceptance Testing is performed by the Client of the 
application to determine whether the application is 
Developed as per the requirements specified by him/her.

it is performed within the development of the organization 
or at the client site.
Alpha testing and Beta testing are the examples of 
Acceptance Testing.

testing done according to the UATest Plan is User 
acceptance testing 

User acceptance testing is done to test the user 
acceptability and after all the requirements are met by the 
system then according to the system test plan we will do 
system testing
the hierarchy is ...  
unit testing
integration testing
system testing
acceptance testing

Objective of UAT : To test the application from end users 
perspective and to verify for the business rules.

Reference document for UAT : BRD

Environment for UAT : Simulated Live Environment(Prod Site)

Data used for UAT : Simulated live data

UAT (user Acceptance Testing ) or 
CAT (client Acceptance Testing ) is done at Client Side.
Clinet verifes that all requirements are  implemented or 
not//

The following question were asked by TCS for Trainees in 
their Mid term exam.what type of question will be done by 
User?
Answer: Acceptance Testing.

User Acceptance Testing :This is the system level 
testing .Generally done at the clients environment . This 
test is done with realistic data of the client to find out 
errors .There are two types of testing ALPHA TESTING & BETA 
TESING.
Alpha testing: Testing an application when development is 
nearing to completion .The minor design changes have to be 
made on basis of alpha testing.This test is done by client 
or cutomer at development site.
Beta testing: Testing when development and testing are 
essentially completed & problems needed to be found before 
final release.This is conducted at one of more customers 
sites by the end users of the software .

UAT(User Acceptance Testing) means the testing carried out 
by the client once the build got deployed(release) into 
their server (ie version controller), through check out 
process. Then the user will check from scrath, like 
spelling mistakes/ whether it meets the exit criteria and 
requirements and also whether all functionality is working 
or not. Once the bug detected in UAT then they call it as 
defect.

the same s/m testing is done in the presence of custamer is 
known as user acceptance testing this is done by the test 
engineer its a black box testing

First we can refer the word users as customers and customers
are those who use the product.So user acceptance testing is
checking how much a new developed system or product is
needed or appriciated by users.The system could be a software
system,applicaton system or what ever.

ya ,
In real time we had done the promotes like 
 
UAT : client  should happy to release the build to 
customers point of level , for that purpose they conducted 
two levels of testing 1. Alpha testing 2 . Beta testing .

Alpha : conducted truely function wise  and done by the 
developers /testers  to process the bussiness rules into 
the application .
Beta : before Promotes / production  client  used to run 
the bussiness wide check lists by covering all the 
functionalities in real env  .
In the beta level co-ordinators and management memebers 
will be overlooked whether the application is performed 
well or not .
Regards,
koteswara.9.rao@gmail.com

Nice info but Testing environment is not mentioned

got few additional details

 Acceptance Testing is the formal testing conducted to
determine whether a software system satisfies its acceptance
criteria and to enable buyer to determine whether to accept
the system or not.Acceptance testing is designed to
determine whether software is fit for use or not. Apart from
functionality of application, other factors related to
business environment also plays an important role.
 

User acceptance testing is different from System Testing.
System testing is invariably performed by the development
team which includes developer and tester. User acceptance
testing on the other hand should be carried out by the end
user. This could be in the form of

    * Alpha Testing - Where test are conducted at the
development site by the end users. Environment can be
controlled a little bit in this case.
    * Beta Testing - Where test are conducted at customer
site and development team do not have any control on the
test environment.

In both the cases, these testing might be assisted by
software testers.

It is very important to define acceptance criteria with the
buyer during the various phases of SDLC. A well defined
acceptance plan will help development/QE teams by
identifying user's need during software development.
Acceptance Test plan must be created or reviewed by
customer. Development team and customer should work together
and make sure that they have

    * Identify interim and final products for acceptance,
acceptance criteria and schedule.
    * Plan how and by whom each acceptance activities will
be performed.
    * Schedule adequate time for buyer's staff to examine
and review the product
    * Prepare the acceptance plan.
    * Perform formal acceptance testing at delivery
    * Make a decision based on the results of acceptance
testing.

Entry Criteria

    * System Testing is completed and defects identified are
either fixed or documented.
    * Acceptance plan is prepared and resources have been
identified.
    * Test environment for the acceptance testing is available

Exit Criteria

    * Acceptance decision is made for the software
    * In case of any caveats, development team is notified

he objective of software development is to develop the 
software that meets the true
needs of the user, not just the system specifications. To 
accomplish this, testers should
work with the users early in a project to clearly define 
the criteria that would make the
software acceptable in meeting the user needs. As much as 
possible, once the
acceptance criterion has been established, they should 
integrate those criteria into all aspects
of development. This same process can be used by software 
testers when users are unavailable
for test; when diverse users use the same software; and for 
beta testing software. Although
acceptance testing is a customer and user responsibility, 
testers normally help develop an
acceptance test plan, include that plan in the system test 
plan to avoid test duplication; and, in
many cases, perform or assist in performing the acceptance 
test.

The objective of software development is to develop the 
software that meets the true needs of the user, not just 
the system specifications. To accomplish this, testers 
should work with the users early in a project to clearly 
define the criteria that would make the software acceptable 
in meeting the user needs. As much as possible, once the
acceptance criterion has been established, they should 
integrate those criteria into all aspects of development. 
This same process can be used by software testers when 
users are unavailable for test; when diverse users use the 
same software; and for beta testing software. Although
acceptance testing is a customer and user responsibility, 
testers normally help develop an acceptance test plan, 
include that plan in the system test plan to avoid test 
duplication; and, in many cases, perform or assist in 
perrforming the acceptance test.

nglmartin@hotmail.com