Skip to main content
All CollectionsCiteOps 25.0
CiteOps 25.0 UAT Guide
CiteOps 25.0 UAT Guide
Elsjene Smit avatar
Written by Elsjene Smit
Updated over a year ago

We’re excited to announce that we are upgrading CiteOps! CiteOps is available for testing for every new and existing CiteOps user on your site's test environment.

We’ve been very lucky to work closely with our users to better understand their daily planning and scheduling processes. We’ve learned a lot, and as a result, refined our task shadowing functionally to allow users to shadow tasks to multiple processes.

In preparing CiteOps 25.0, our team has gone through the reiterative process of development and quality assurance testing, and we are now at the stage of User Acceptance Testing (UAT). The UAT stage gives our users the ability to test CiteOps 25.0 against their daily operational requirements. This stage also acts as our last screening for any potential bugs due to company or user-specific edge cases that may not have been catered for in our internal quality assurance test scripts.

So, what is expected from you as the user? Below you will find a high-level overview of the general functionalities that should be tested. Please note that this is the minimum level of testing that users are expected to conduct, and this article should only be used as a guide. Ideally, you should mimic your daily usage of CiteOps in this test environment to ensure all user-specific edge cases are working as expected.

UAT GUIDE

PLANNERS & COORDINATORS (Planning Board & Schedule Screens)

  • Put together a typical shift plan

  • Shadow tasks (some accepted, some rejected, some pending)

  • Lend people and equipment between different processes

  • Edit task notes as you normally would

  • Duplicate tasks and drag them to a different shift

  • Print any shift plans or custom reports as you normally would

  • Test all task smart imports

  • Create a new form, edit an existing form

  • Check any calculated KPIs, autotags or compliance policies

  • Print shift plan and review all details

  • If your site has any integrations or BiPoint reports set up, test them

DEPUTIES & SUPERVISORS (Actuals Screen)

  • Close out tasks with task notes (test all scenarios: fully complete some tasks, have tasks not started, and partially complete some tasks)

  • Close of manual KPI actuals (try all scenarios: meet KPI exactly, underperform, overperform)

  • Complete any shift checklists

  • Fill out the Shift Report screen

HR REPRESENTATIVE (Roster Screen)

  • Test all people-related smart imports

  • Add leave for every relevant leave type to various types of users

  • Add overtime to various types of users

  • Move users to a new process

  • Move users to a new work schedule rule

EQUIPMENT SCHEDULER (Equipment Scheduler Screen)

  • Test all equipment-related smart imports

  • Move pieces of equipment to different default processes and check that the changes are reflected in the availability boxes

Did this answer your question?