VCE IT Theory Slideshows By Mark Kellymark@vceit.com

Vceit.comUser Acceptance Testing

Contents

• Other testing types• User Acceptance Testing

Unit testing

• Testing a component of a system (e.g. a subprogram or hardware part) in isolation to see that it does what it’s supposed to do.

Integration Testing

• Joining the component (software or hardware) to see that it behaves properly when joined to related components.

• E.g. does a subprogram accept parameters or return values correctly to/from another subprogram?

• Is a piece of hardware pin-compatible with the device it plugs into?

System Testing

• Finding out whether the entire system with all of its components is working as it should.

User Acceptance Testing (UAT)

• Formal testing of whether the intended user of the system or product is happy the way it carries out its functional and non-functional requirements, as specified in the SRS.

UAT• The project schedule may say all tasks are

done…• The programmers may have cleared all known

bugs…• So why wont the client settle their account

and let you get on with your next project?• They want a demonstration that you have

delivered on everything you promised.• That’s why you do User Acceptance Testing.

Before UAT

• Informal testing (testing as you go during development is finished.

• Integration testing is finished.• The testing environment has been set up and

test methodology agreed on.• Test data has been agreed on.• Criteria for success have been agreed on.

During UAT

• Actual end-users are often used for UAT rather than managers

• Skilled users can tell if a product has problems that a mere observer could never notice

• In fact, modern developers seek end user input during design and development to avoid nasty surprises during UAT

What is the purpose of UAT?

• To demonstrate that the system is fit for real use by real people in the business.

• Is different to system testing which proves that the system behaves in the way that was described in the SRS.

• A product could satisfy the SRS but be a never-ending pain for its users.

What UAT sounds like

Developer: The product should respond briskly. I click here, and we get instant response.

User: OK.Developer: The product should be easy to read. See the font size

and colours we used? OK?User: They’re fine.Developer: Help needs to be contextual. See, I open this and

press F1 – relevant help appears.User: Yep. OK.Developer: Next, we had to make it disaster resistant. I’ll just

pull out the power cord and see how it avoids data loss…

After UAT

• User signs off on the product, accepting that it is satisfactory. Then the developer can be paid.

• Any known defects that will not interfere with a commercial released are identified, and fixes are scheduled.

• If functionality is unacceptable, a timeline is established with the developer to fix the problems and resubmit the problem for UAT.

By Mark Kellymark@vceit.comvceit.com

These slideshows may be freely used, modified or distributed by teachers and students anywhere on the planet (but not elsewhere).

They may NOT be sold. They must NOT be redistributed if you modify them.

VCE IT THEORY SLIDESHOWS