Required Fields Validation Ratatouille
This robust dish ensures the required fields on a change password form are appropriately denoted and validated.
Instructions
You are an experienced QA professional focused on comprehensive test coverage, testing of edge cases and thorough QA of tested features.
All test results should be reported in tabular format which includes the following columns: test case #, test case, expected, actual and result. Test results should also include a defect log and test summary. Follow the sections and format used in the attached sample_test_report_gene_ tools.md file as an example of what to include in the report.
Skills
/gene-tools-website-login (implicitly triggered via prompt)
Files
Project File - sample_test_report_gene_ tools.md
Prompt
Write and execute a test plan to verify that all fields which are required on this form are marked with an * at the end of the field label: https://dev-genetools.useast01.umbraco.io/ my-account/ change-password/
Prep Time: 5 minutes
Cook Time: 5 minutes
I need to scroll down to find the login form.
I can see the login form. Let me scroll up to fill in credentials.
I need to scroll down a bit to find the username field.
I can see the login form. Let me fill in the credentials.
Credentials are filled in. Please complete the reCAPTCHA "I'm not a robot" checkbox in your browser, then let me know when you're done so I can click the Login button.
It seems I scrolled past the login button. Let me scroll back up and find it.
reCAPTCHA is checked. Now let me scroll down to click the Login button.
Logged in successfully. Now let me navigate to the Change Password page and inspect it thoroughly.
I can see the full form now. Let me use JavaScript to do a thorough DOM inspection of all fields — their labels, IDs, and data-val-required attributes.
Now let me take a full-page screenshot to visually confirm labels, and also check for any additional validation rules (e.g. regex/length validators) and whether the "Change Password" button has any notable attributes.
I now have all the data I need. Let me take a final zoomed screenshot of the form for visual confirmation, then produce the report.
I have all the data needed. Now let me produce the test report.
Now I have everything I need. Let me produce the markdown report.
The test plan has been executed and the report is complete. Here's a summary of findings:
Result: All 3 tests PASS — 100% pass rate, 0 defects.
The Change Password form at /my-account/change-password/ is a straightforward single-section form with exactly three fields, all of which carry data-val-required server-side validation. All three labels correctly display the * asterisk indicator:
Field | Field ID | Label Displayed | Result |
|---|---|---|---|
Current Password |
| "Current Password *" | ✓ PASS |
New Password |
| "New Password *" | ✓ PASS |
Confirm Password |
| "Confirm Password *" | ✓ PASS |
One secondary observation worth noting: the Confirm Password field also uses a data-val-equalto cross-field validator to ensure it matches New Password — that's implemented correctly but was out of scope for this test.