BE99 DEV test sandbox · Live run · Thu, 29 Oct 2026, 10:52 pm AEST
Pronto 2.0 Test Results
Each check creates a real job in the Pronto test sandbox, runs it through the Obzervr integration the way a site would, and reads the result back from both systems.
- Checks run
- 1
- Working
- 1
- Problems found
- 0
- Needs a look
- 0
- Not set up yet
- 0
- Test jobs created
- 1
What this run tells us
1 of 1 checks passed. No check found a known problem in the integration.
- 1 working
- 32 not run this time
Every check, by area
Show
Jobs coming from Pronto into Obzervr
1 of 7 working| What we check | Result | What happened |
|---|---|---|
| A planned job raised in Pronto appears in Obzervr with all its detailsPWO-P2O-01 | Working | All steps passed.Pronto job 026375 |
| Labour requirements come across, including changes and deletionsLAB-01 | Not run this time | Not selected for this run. |
| Each work type (PM, breakdown, corrective and BE99's extra types) comes acrossPWO-P2O-02 | Not run this time | Not selected for this run. |
| Bulk status and date changes in Pronto update ObzervrPWO-P2O-03 | Not run this time | Not selected for this run. |
| Plant items with several monitor points come acrossPWO-P2O-04 | Not run this time | Not selected for this run. |
| Pronto keeps a link back to the Obzervr jobPWO-P2O-07 | Not run this time | Not selected for this run. |
| Quick links on a Pronto job show in ObzervrQL-01 | Not run this time | Not selected for this run. |
Completing jobs back to Pronto
0 of 11 working| What we check | Result | What happened |
|---|---|---|
| Completing a planned (PM) job updates Pronto: notes, times and hoursPWO-O2P-01 | Not run this time | Left out by live-safe mode, because it completes, finalises or cancels a job. |
| A break-in job raised in Obzervr is created in Pronto with every fieldBWO-01 | Not run this time | Not selected for this run. |
| Different kinds of timesheet entry on a break-in job reach ProntoBWO-02 | Not run this time | Not selected for this run. |
| Finishing one section of a job sends it to Pronto straight away, onceGIC-01 | Not run this time | Not selected for this run. |
| Materials on a job are kept in step between Pronto and ObzervrMAT-01 | Not run this time | Not selected for this run. |
| Completing a planned (PM) job updates Pronto: notes, times and hoursPWO-O2P-01 | Not run this time | Not selected for this run. |
| Completing a breakdown job updates ProntoPWO-O2P-02 | Not run this time | Not selected for this run. |
| Completing a corrective job updates ProntoPWO-O2P-03 | Not run this time | Not selected for this run. |
| When Pronto refuses to finalise a job, the refusal is handled cleanlyPWO-O2P-05 | Not run this time | Not selected for this run. |
| Fault codes, downtime and finish date reach Pronto on completionPWO-O2P-06 | Not run this time | Not selected for this run. |
| A job Pronto has already finished isn't changed by a later cancelPWO-O2P-09 | Not run this time | Not selected for this run. |
Cancelling and putting jobs on hold
0 of 6 working| What we check | Result | What happened |
|---|---|---|
| Cancelling a job in Obzervr cancels it in ProntoWOSC-01 | Not run this time | Left out by live-safe mode, because it completes, finalises or cancels a job. |
| Cancelling a job in Obzervr cancels it in ProntoWOSC-01 | Not run this time | Not selected for this run. |
| Putting a job on hold with a coded reason puts it on hold in ProntoWOSC-02 | Not run this time | Not selected for this run. |
| Putting a job on hold with an 'Other' free-text reasonWOSC-03 | Not run this time | Not selected for this run. |
| A coded hold reason that needs a comment carries the comment to ProntoWOSC-04 | Not run this time | Not selected for this run. |
| Cancelling after a job is finalised leaves the Pronto job finishedWOSC-05 | Not run this time | Not selected for this run. |
Work requests
0 of 4 working| What we check | Result | What happened |
|---|---|---|
| A work request raised inside a job carries every field to ProntoWR-01 | Not run this time | Not selected for this run. |
| A standalone work request reaches ProntoWR-02 | Not run this time | Not selected for this run. |
| A work request raised inside a planned job reaches ProntoWR-03 | Not run this time | Not selected for this run. |
| A work request with a blank Requested By doesn't fail or loopWR-04 | Not run this time | Not selected for this run. |
Stock, readings and master data
0 of 5 working| What we check | Result | What happened |
|---|---|---|
| Master data record counts match between Pronto and ObzervrMDS-COUNT-RECONCILE | Not run this time | Not selected for this run. |
| New monitor points in Pronto are created in ObzervrMP-01 | Not run this time | Not selected for this run. |
| Monitor point readings: update, correct and deleteMP-02 | Not run this time | Not selected for this run. |
| Plant readings taken in Obzervr reach ProntoPWO-O2P-04 | Not run this time | Not selected for this run. |
| A stock order raised in Obzervr reaches ProntoSO-01 | Not run this time | Not selected for this run. |
How much of the UAT workbook this covers
The customer's UAT workbook has 221 rows that BAs test by hand before a release. This is where each row stands after this run.
- 11 checked automatically and passed
- 111 automated, but not run this time
- 65 still needs a person to check
- 21 can't be automated (emails, pdfs, tablet)
- 13 dropped from uat on purpose
How to read the results
Working
The integration did what it should, checked in both Pronto and Obzervr.
Problem found
The integration did something wrong. It has a Jira ticket.
Needs a look
The check didn't pass and the team hasn't said why yet, or it hit a test or sandbox issue.
Not set up yet
The sandbox is missing a setting the check needs, so it didn't run.