PBES UAT and E2E Tester Manual
Objective
Use this guide to assess the public PBES website as a visitor would, record observed outcomes, and submit actionable feedback. Test the deployed or designated staging site, not an assumed behavior. Do not enter real customer information unless specifically authorized.
Start a Test
- Open the PBES E2E test form or select the E2E testing service from the Client Service Hub homepage.
- Optionally enter your name and email. Enter device, browser, and user type so issues can be reproduced and results can be interpreted. Tester details are optional.
- Keep the PBES site open in a separate tab and work through the test groups in order, or select the journeys relevant to your assigned role.
Record Each Test Case
For each case, perform the listed action and compare what you observed with its expected result. Select one status:
- Pass: The observed behavior matches the expected result.
- Fail: The behavior differs, is broken, or blocks the task.
- Blocked: You could not reach a meaningful result because of an external dependency, missing access, or another blocker. Explain what blocked you.
- Not run: You did not execute the case. Leave unrelated cases as Not run instead of guessing.
Add a short, factual comment for failures, blocked cases, or anything that needs context. Include the steps to reproduce, the page or control involved, and the actual result. Do not mark a case Pass merely because the page loaded if the expected interaction was not tested.
Test Groups
Homepage: HP-001 to HP-003
Open the homepage, assess whether the PBES value proposition is understandable, and check that service links and descriptions make sense.
Farmer journey: FARMER-01 to FARMER-08
Review the biogas offering, open the relevant estimator, enter realistic test values, generate an estimate, locate a quotation form, and exercise quotation/contact submission only with approved test data. Record external-service failures as Blocked or Fail with the reason; never submit a real quotation request unless authorized.
Investor journey: INVESTOR-01 to INVESTOR-05
Review the company overview, story, team, services, and contact path. Record whether the mission, business model, leadership, and value proposition are clear.
Negative tests: NEG-001 to NEG-004
Check blank quotation submission, invalid email handling, special-character handling, and empty estimator values. Use synthetic values only. Record whether validation blocks or explains invalid input as expected.
Mobile: MOB-001 to MOB-003
Check layout and navigation on Android, iPhone, and tablet-sized devices where available. Include the actual device/browser in tester information and note any overlap, clipping, or inaccessible controls.
Record Defects
Use Add defect for each distinct issue. Provide a concise title and description; choose severity and status; include the module and a screenshot filename/reference if available. A filename/reference is text only: the form does not upload screenshots. Do not include passwords, tokens, private customer information, or sensitive account data in defect details.
Severity reference:
- P1 Critical: Core business process blocked, such as a quotation request that cannot be submitted.
- P2 High: Major feature is broken, such as an estimator that fails.
- P3 Medium: Feature works but has a material usability or validation issue.
- P4 Low: Cosmetic or minor content issue.
Submit the Report
- Complete at least one test case with a status other than Not run.
- Enter overall feedback in What should we improve? This field is required.
- Choose Approved or Not approved for UAT sign-off. This is required; choose Not approved if acceptance criteria are not met.
- The ease-of-use rating is optional.
- Contact consent is optional. If selected, provide a valid email address.
- Select Submit test report once. Wait for the confirmation and save the displayed report reference number for follow-up.
The server enforces the required fields and accepts up to 40 test cases and 30 defects per report. Invalid reports show an error and are not saved; correct the issue and submit again.
Acceptance Guidance
A report is useful when it reflects observed behavior, unrun cases are clearly left Not run, failures include reproducible details, and the final sign-off matches the evidence. Report blockers honestly; do not alter production data or contact real customers during testing without authorization.