Quality is delighting customers
1. Data integrity
The complete data belonging to each entity should be stored in the database. Depending on the database design, the data may be present in a single table or multiple related tables. Parent-child relationships should exist in the data. There should not be any missing data.
2. Correctness of the data stored in the database
The data should be present in the correct table and correct field within the table.
3. Correctness and completeness of data migration (in case some or all the original data has come from another source)
4. Functionality and performance of user objects e.g. functions, procedures, triggers.
5. Database performance (query execution times, throughput etc.) and locking problems
You may identify the main queries (or procedures) that are used in the application and time them with sample data. Locking problems may become apparent when multiple inserts/ updates are being made
to the same entity simultaneously.
6. Data security
You may check if any data that should be encrypted e.g. passwords, credit card numbers is in plain text or not. The database should not have the default passwords. Even application accounts should have passwords that are complex and not easily guessed.
Additionally, you might need to review the following items:
1. Database fields (if they meet the specifications e.g. width, data type etc. as given in the design documentation/ data dictionary etc.)
2. Normalization level
3. Compliance of user objects code to coding guidelines
In order to perform database testing, you should be good at using the database tools and writing SQL queries.
Comments are closed for this blog post