Pasta topped w Verifying Required Fields Indicators
This robust dish ensures the required fields on a login 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.
If prompted to login to the front-end of the site, use the following credentials: username = JWTest, password = ********
If prompted to login to the backoffice or cms, use the following credentials: username = jen@proworks.com, password = ********
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.proworks.io/login/
Cook Time
5 min.
Good, the page has loaded. Now let me start the GIF recording and begin the test.
The page is loaded. I can see the "Incident Updates" section and an "Add Incident Update" button. Let me click it to expand a new update form.
I need to scroll down to see if the button click opened a new update form. Let me scroll down first.
I can see the "Add Incident Update" button. I need to click it to open a new incident update form. Let me click it now.
A new incident update has been added and I can see the Author field with a "-- Select Author --" dropdown. Now let me click the dropdown to inspect its options.
The dropdown is focused. Let me use JavaScript to extract all the options from the Author dropdown to verify them programmatically.
I have all the data I need. Let me now capture the final screenshot of the open dropdown and stop the recording.
Now let me open the dropdown and take a zoomed screenshot showing all options.
All tests have been executed. Here is the complete test report:
✅ Test Report — Author Field in Incident Update Form
URL: https://employee.fire.calfire.proworks.io/incident-form/?id=dbb217cf-cee8-4d3d-b356-1154f4eab6ab Date: April 13, 2026 Tester: Claude (automated)
Test Cases & Results
# | Test Case | Expected | Actual | Result |
|---|---|---|---|---|
TC-01 | Page loads successfully | Page renders with Incident Form | Page loaded with all sections visible | ✅ PASS |
TC-02 | "Add Incident Update" button is present | Button visible in Incident Updates section | Button found and clickable | ✅ PASS |
TC-03 | Clicking button reveals a new update form | A new expandable update entry appears | New update "Untitled Incident Update 4" expanded with form fields | ✅ PASS |
TC-04 | Author field is present in the form | A field labeled "Author" exists | Field labeled Author confirmed present | ✅ PASS |
TC-05 | Author field is a dropdown (SELECT element) | Input type is a | Element type confirmed as | ✅ PASS |
TC-06 | Dropdown contains "Incident Management Team" | Option present | ✅ Present | ✅ PASS |
TC-07 | Dropdown contains "Intel" | Option present | ✅ Present | ✅ PASS |
TC-08 | Dropdown contains "Public Information Officer" | Option present | ✅ Present | ✅ PASS |
TC-09 | Dropdown contains "Webtech" | Option present | ✅ Present | ✅ PASS |
TC-10 | No unexpected extra options exist | Exactly 4 options (excluding placeholder) | Exactly 4 options — no extras found | ✅ PASS |
Summary
10 / 10 tests passed. 0 failures.
The Author field is present, is correctly implemented as a dropdown, and contains exactly the four expected options in the following order:
Incident Management Team
Intel
Public Information Officer
Webtech
A GIF recording of the test session has been downloaded as author-field-test.gif.