Writing Test Cases
Writing Test Cases for Database Validation
This prompt helps engineering and QA teams create test cases to validate database functionality, including CRUD operations, data integrity, and performance. It focuses on ensuring that the database performs reliably under various scenarios and aligns with application requirements.
Responsible:
Engineering/IT
Accountable, Informed or Consulted:
Engineering, QA
THE PREP
Creating effective prompts involves tailoring them with detailed, relevant information and uploading documents that provide the best context. Prompts act as a framework to guide the response, but specificity and customization ensure the most accurate and helpful results. Use these prep tips to get the most out of this prompt:
Gather the database schema, including table definitions, constraints, and relationships.
Define test data sets, including valid and edge-case scenarios.
Set up database access and tools for executing and monitoring queries.
THE PROMPT
Help create detailed test cases for validating the database functionality of [specific application or feature]. Focus on:
CRUD Operations: Recommending scenarios, such as, ‘Verify Create, Read, Update, and Delete operations for specific tables and ensure they work as expected with valid and invalid inputs.’
Data Integrity Checks: Suggesting validations, like, ‘Test constraints, such as primary keys, foreign keys, and unique constraints, to ensure data consistency.’
Performance Testing: Including benchmarks, such as, ‘Measure query execution times under varying loads and evaluate index performance for frequent queries.’
Error Handling: Proposing failure scenarios, like, ‘Test how the database handles errors, such as null values in mandatory fields or exceeding column length limits.’
Backup and Recovery Validation: Recommending reliability checks, such as, ‘Ensure that backups are successfully created and that data can be restored accurately without corruption.’
Provide a structured set of database test cases that ensure robust performance, data integrity, and compliance with application requirements. If additional details about the schema or specific database operations are needed, ask clarifying questions to refine the test cases.
Bonus Add-On Prompts
Propose strategies for automating database test cases using tools like SQLMap or DbFit.
Suggest methods for validating database schema changes during application updates.
Highlight techniques for testing database transactions and rollback operations.
Use AI responsibly by verifying its outputs, as it may occasionally generate inaccurate or incomplete information. Treat AI as a tool to support your decision-making, ensuring human oversight and professional judgment for critical or sensitive use cases.
SUGGESTIONS TO IMPROVE
Focus on testing specific database operations, such as stored procedures or triggers.
Include tips for validating database security, such as user permissions and encryption.
Propose ways to simulate high-concurrency scenarios to test database locking and deadlocks.
Highlight tools like pgAdmin, MySQL Workbench, or Oracle SQL Developer for testing workflows.
Add suggestions for documenting performance baselines to track improvements over time.
WHEN TO USE
During development or maintenance of database-driven applications.
To ensure data consistency and reliability after schema updates or migrations.
When optimizing database queries or addressing performance issues.
WHEN NOT TO USE
For non-relational systems that do not require database validations.
If database access or schema details are unavailable.