Test planning
Connect requirements to scenarios, expected results and owners.
User acceptance testing (UAT) is the stage where the people who will use a solution confirm it works for their real tasks before it goes live. Umbrella Tech provides IT testing services for Australian organisations, combining technical checks with UAT built around business scenarios, then recording results, defects and retests as evidence that the solution is ready to rely on.
A solution can be installed correctly and still fail once real users, integrations or recovery processes are involved. Acceptance needs evidence that covers the intended use, rather than a general declaration that the project is finished.
A clear basis for acceptance and handover, with every requirement linked to a test and a result. Validation also identifies the changes needed before the solution can be relied on in normal operation.
Connect requirements to scenarios, expected results and owners.
Run agreed functional, access, integration, performance and failover checks.
Prepare scripts, coordinate business testers and capture their results.
Record results, defects, retests and accepted exceptions.
Agree what will be tested, by whom, against which criteria.
Write test cases, set up test data and accounts, and brief the testers.
Run the tests, log defects and retest fixes.
Report results, record accepted exceptions and obtain sign-off.
After an onsite firewall, switch and Wi-Fi replacement for an IT provider's client, we tested internet, Wi-Fi, printing, VPN and desk phones and had each confirmed by the staff on site. Read the Rosh Tech case study.
Can't see your question? Ask us directly →
Testing carried out by business users, or on their behalf against their scenarios, to confirm a solution supports their work before it is accepted. It complements technical testing rather than replacing it.
On any change that affects how people work: new systems, migrations, network replacements or automation. It matters most when the delivery team and the users are different people.
Business users should validate the scenarios relevant to their work. We prepare and coordinate the testing, while technical checks and acceptance responsibilities are agreed in the test plan.
It depends on the number of requirements and scenarios, tester availability and how many defects need retesting. Scope and timing are confirmed in discovery.
Test data that does not expose real personal information, test accounts removed afterwards, and a clear record of who accepted any known exception. Testing can be part of a wider Technology Project Delivery engagement.
Tell us what is being delivered and how you plan to accept it. We will help define a practical starting point.