¶ In this lesson you will
- Prepare a new service for testing
- Open it on a portal in test mode
- Know what differs for an improvement
A new service: Prepare For Testing
- Prepare For Testing: publishes your current configuration to the test environment
- Save & Close
- Submit to QA
- Toast confirming the change request was updated
Prepared: the button becomes Test Service
- Test Service: try the service as a citizen
- Preview Form: toggle form preview
- Save & Close: save and leave
- Submit to QA: send for review
- Global translation note: key cannot be edited here
Test Service: choose the portal
- Citizen Portal
- Irembo Plus (agents)
- RDB OSC (one-stop centre)
- Test Service opens the portal in developer mode
- Close
Test Service opens /dev/service/details?id=…&changeRequestId=… on the chosen portal. Sign in with a test applicant account and apply exactly as a citizen would. Payments on staging are sandbox payments.
Testing a new service vs an improvement
| New service | Service Improvement | |
|---|---|---|
| Prepare For Testing | Yes, once, before the first test | No: the improvement shows Test Service directly |
| Test Service portals | Citizen Portal, Irembo Plus, RDB OSC | Same |
| After each change | Save the step, then test again | Same |
Gotcha · test every branch, not only the happy path
Apply, pay, approve, and also reject, request for action, resubmit, and let a bill expire. Our demo failures (Section D) all hid in branches nobody had clicked.
Tip · open the browser console while testing
Keep DevTools open (F12 or Cmd+Opt+I). A red error on submit gives you a
traceIdto search in Kibana (lesson D6).