User Acceptance Testing - Overview

“The principle objective of software testing is to give confidence in the software.”

Stephen Newton
Service Acceptance Test Manager 03 Sept’ 2015
Agenda

• Introduction
• UAT Goals
• What to Expect
• Testing Milestones
• Feedback
• Next Steps

© 2015 Unisys Corporation. All rights reserved. 2

Introduction

• A key component of the migration activities prior to

assumption of service is User Acceptance Testing (UAT).

• UAT involves Constellium ‘end users’ testing the new

processes and providing feedback to help us gauge the
overall readiness to ‘Go-Live’ with the delivery of the
managed solution.

• UAT will require you and individuals from your team to

participate in an exercise that tests the service support
processes.

© 2015 Unisys Corporation. All rights reserved. 3

UAT Goals

• The primary goal of the test is to assess the readiness of the

managed solution for steady state operations
• The secondary goal is to gain feedback on the Service Desk
and Field operations to provide information on gaps and
areas for improvement before we enter steady state
operations (Including Training, Knowledge Base Articles and
tooling)
• Testing will also validate the technology employed to support
the Constellium solution and the back office support
resources

© 2015 Unisys Corporation. All rights reserved. 4

Roles and Responsibilities

Test Coordinators : -
• Liaise with End Users
• Share and run the test scripts
• Check for results, gather details around the issues/problems encountered
• Attend wash up meetings.
Test Manager Stephen Newton: -
• Schedule and Chair the Check-Point meetings daily for the entire duration of
UAT
• Triage issues in the defect log
• Liaise with Technical Teams for resolution of open issues
• Produce and Communicate the daily status report to stakeholders at the end of
each day during UAT

© 2015 Unisys Corporation. All rights reserved. 5

Before Testing – What to do

Check:
• Can you login to the tools and systems
• Do you have the correct access and permissions to perform
your tasks
• Are you in the correct groups (Where appropriate)

© 2015 Unisys Corporation. All rights reserved. 6

Day of Testing –
End Users what to do/expect
• Please follow the test schedule provided to make sure you
are available to perform your part in the testing
• Make yourself familiar with the test scenario being run
• Make sure the Service Desk agent is aware that this is a test
call and state the test number
• Record your results on the feedback forms for feed back to
your Test Coordinator. The Test Coordinator will update all
the results on the xNet portal prior to a daily meeting.
• Any issues will be triaged by the Test Manager who will
arrange fixing and re-testing

© 2015 Unisys Corporation. All rights reserved. 7

Logs

Test Log Issues Log

• https://xnet.unisys.com/sites/6467988 • https://xnet.unisys.com/sites/6467988/GC/
/GC/Lists/UAT%20Test%20Log/AllIte Lists/UAT%20Problem%20Log/AllItems.a
ms.aspx spx

© 2015 Unisys Corporation. All rights reserved. 8

Completing Logs

• Either change the view to ‘Edit’ view

• Or click on the item and then the Edit button

© 2015 Unisys Corporation. All rights reserved. 9

Call Survey Log

• We also have a ‘Call Survey Log’

• Much like a CSAT for UAT
• Please complete this at the time of the call
– Note: The ticket number and Agent name are important for tracing
the call and either investigating issues or learning from good
examples
• Each day the completed sheets should be returned to your
Test Coordinator to merge and send to the Test Manager
who will combine all responses, analyse and add to the daily
report.

© 2015 Unisys Corporation. All rights reserved. 10

Day of Testing –
Agents what to do/expect
• Please follow the test schedule provided to make sure you
are available to perform your part in the testing
• When you record the Incident or Request in tools prefix the
ticket title with the words “TESTING PLEASE IGNORE +
“Test Case ID”” to ensure we do not generate responses
from resolvers or End Users and can perform clean up
activities post UAT
• Follow the support procedures as outlined in the KB
• Record you results on the test script provided for feed back
to your Test Coordinator. At the end of the days testing the
Test Coordinator will bring all the results to a meeting for
discussion. Any bugs will be triaged by the Test Manager
who will arrange fixing and re-testing
© 2015 Unisys Corporation. All rights reserved. 11
Testing Milestones

Date Duration Milestone Description

03 Sept’ 2015 30 Mins UAT Launch Presentation to prepare for the start of testing

31 Aug’ 20915 1 Week FAT (Internal Unisys internal dry run to confirm agents, tests and tools readiness for
Testing) UAT

7 Sept’ 2015 2 Weeks UAT Constellium End User and Unisys joint testing the full solution

© 2015 Unisys Corporation. All rights reserved. 12

Testing Checkpoints

• Through out the testing cycles are daily status calls for the
Test Coordinators and Stakeholders
• Agenda
– Progress against tests
– Current status of the issue log
– New issues for the log
– Actions for the next day
– A.O.B.
• The meeting invites have been sent, if you do not have them
or feel someone is missing please let me know.

© 2015 Unisys Corporation. All rights reserved. 13

Next Steps

• Execute Test scenarios/evaluation forms

• If you are unable to take part in the testing or need more
information or help, please make your Test Coordinator
and/or the Test Manager aware.
• Review and report results

© 2015 Unisys Corporation. All rights reserved. 14

Questions

© 2015 Unisys Corporation. All rights reserved. 15