Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Having e.g. a system for booking flights, during UAT it is not being tested by real users (customers who will buy tickets) rather than people from the client side who will just simulate this. Are there any more specific terms to distinquish between real users (like end user) and users doing the UAT?

share|improve this question
How abt END USERS and clients? – Milee Sep 10 '12 at 6:13
I don't think the acronym for Stake Holder Acceptance Testing would go well with project documentation :) – Simon Whitehead Sep 10 '12 at 6:32
If I get you right, you seem to have a problem calling someone who does acceptance testing just an "acceptance tester" - where is the catch? – Doc Brown Sep 10 '12 at 12:22
This may sound like a shameless advert, but in the past, I've used to get third-party "end-user" testing. It's a great service. – Ryan Kinal Sep 10 '12 at 15:15
@RyanKinal, I'm sorry, but this doesn't only sound like a shameless advert in my opinion :P – mcwise Sep 11 '12 at 14:22

The customers who are going to buy ticket are not the real users of the application.
Real users are those who are going to deploy the application and will be operating the system.

Customers will just be requesting for the ticket, mentioning their details (not filling any of the details at their own). The employees of the company will be operating the application, filling the details mentioned by the customer and filling other requirements.

So, the employees will be the real users. They participate in testing, as they need to customize the application as per their requirements.

share|improve this answer

The distinction doesn't matter. Your acceptance testing should encompass all of the functionality that is exposed to the end user. You absolutely should test it as if you were the end user, as well as testing edge cases and unusual scenarios that may only affect a handful of end users.

share|improve this answer

Where I work, we are building an internal application and use the terms 'the business' (which are the real end users) and 'testers' (those who do the UATs).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.