qa-test-crud

Automate CRUD testing on admin list pages by creating, editing, and deleting records through the UI while using marker-based cleanup to remove test data, ensuring no junk records persist. This approach validates forms, persistence, and row-level actions end to end.

The best way to test CRUD forms in data management screens is to open the add form, submit generic field data, and verify the new record appears in the list. Reopening the row to edit and delete confirms full persistence and action button functionality.

Yes, you can validate nullable dropdown clearing behavior during the edit flow. The process reopens a created row, updates a field, and can specifically test whether clearing a nullable dropdown saves correctly and persists across the UI.

Yes, CRUD list page testing requires visible add, edit, and delete affordances on the screen. It applies to interactive admin or data-management workflows with tables, grids, and row-level actions, relying on form submission handling and success or error feedback detection.

CRUD tests can fail to clean up records if marker-based cleanup logic is interrupted. This Skill performs deletion and confirms removal even during partial run failures, but broken forms or missing action buttons can prevent the delete flow from executing correctly.

To validate the full CRUD lifecycle on a table or grid view, create a record via the add form, verify it in the list, edit the row to update fields, confirm the change saves, then delete the test record and verify removal with cleanup.