A key contributor to End-to-End (E2E) testing success is the collection of user stories created with input from business units involved in UT Works testing. User Stories, which are comprehensive real-world scenarios, allow testers to use the system the same way their co-workers will use UT Works after go-live. Being able to evaluate how UT Works will perform in “on-the-job” situations is key to the successful adoption of the system. Using real-world scenarios means that some user stories are very specific and recognizable.
User Story Example
User stories include a scenario spelling out what the issue is and how it would be addressed, along with related steps and notes that help the testers know how to use UT Works to accomplish the goal.
FOM – Zone Maintenance Scenario
After the initial investigation of a broken/leaking sink, the crew leader needs to use UT Works (AiM module) to add additional work tasks and work crews to the Work Order, including an Environmental Health & Safety crew (EHS) to test for the presence of asbestos, a plumbing crew to repair the sink, a carpentry crew for sheetrock repair, and painting, and finally a custodial crew for cleanup.
In UT Works, the crew leader uses AiM to add multiple phases to the same work order for the different trades and shops involved in fixing the broken/leaking sink. The technicians and work crew members are assigned work orders by the crew leader in the AiM module and can then view and update their assignments using the Go Work Management on their mobile devices.
The use of scenarios like this help demonstrate and test how a maintenance zone adds additional work tasks and work crews to the initial Work Order and how the system will handle work that involves multiple units and work crews.
To date, this method of testing has been used to test various Service Request scenarios for Facilities Operations & Maintenance (FOM), Landscape & Integrated Building Services (LIBS), and Utilities & Energy Management (UEM).
Example scenarios involved in Service Request testing include:
- Scheduling work orders based on priority, technician capability, and availability
- Scheduling high-priority work
- Scheduling emergency work
- Scheduling after-hours work
- Requesting parts
- Scheduling a work order with multiple phases of work to be completed by different units across Facilities Services.
Additional Testing Updates
- Integration (connections between UT Works and other systems) testing kicked off at the end of May
- Preventive Maintenance testing began in mid-June and will continue through July.
- Testing for Finance scenarios and CPPM are in the planning stages and will begin in late July and extend into August.