UAT/BAT

BAT (Business Acceptance Testing) is also referred to as UAT (User Acceptance Testing)

UAT/BAT is a process that obtains confirmation that a system meets mutually agreed-upon requirements. The UAT acts as a verification of the required business function and proper functioning of the system, emulating real-world usage conditions.

Below is an outline, some pieces from different documents, and some comments from experience. A lot of the time UAT/BAT is looked at as ‘pure’ testing activity, but really it can be that and a training or change artifact. Unfortunately this training or change portion is not discussed/documented much.

  • In an environment that replicates Production (or Pre prod)
  • lifecycle in nature (including exceptions)
    • a resource raises a PO for a widget
    • this exceeds his financial delegation
    • the request is signed off by the correct resource
    • the widget is purchased
    • the widget is delivered
    • the PO is closed
    • the transaction appears in the correct journal
  • Nothing should happen in UAT/BAT for the first time – what you are doing should have been done in system/integration test
  • It is Black box in nature (i.e. it is a method of software testing that examines the functionality of an application (e.g. what the software does) without peering into its internal structures or workings
  • You should have two resources working with the business resource
    • 1 to lead the session and ‘guide’ the testing
    • 1 to capture all the issues and work on resolution and understanding
  • You should start each day with
    • Issues found previous day
    • Issue resolution
    • Business process
    • Suck it and see
    • Accept
    • Defect
    • Etc
  • If you are finding defects then you are either performing BAT to early or the previous testing (System) has not been rigorous enough. You should be finding requirement issues (Change Requests)
  • I strongly suggest you co-locate the resource so you can manage the expectations
  • Things to think about testing
    • The application
    • Training material
    • User guides
    • Quick references
    • BOK

In testing you always need a definition of Quality and an Outcome, so for BAT you could uses something like;

BATs role is to prove the Quality of the application and supporting collateral by proving the presence of that which satisfies users, customers, and other stakeholders, and the absence of that which dissatisfies them. A quality system is fit for the users’ purposes, provides the needed features, and contains few, if any, operationally impacting defects (I have based this on definitions by JM Juran).

When Business Acceptance Testers return to their business roles after completing BAT, they are more knowledgeable about the applications and can act as Champions and SMEs for the applications under test.

 

I recommend reading

http://www.irm.com.au/papers/Managers_Guide_to_User_Acceptance_Testing.PDF

http://blog.8thlight.com/doug-bradbury/2011/04/26/ten-ways-to-do-acceptance-testing-wrong.html

 

If you are feeling really brave you could read the first 25 pages of this

http://testingguidance.codeplex.com/downloads/get/89573#

 

Leave a Reply

Your email address will not be published. Required fields are marked *