Updated: Jan 19
When a user performs operations on the browser (Client-Side), the requests are sent to the back-end server that stores the application records in a dedicated database (SQL, Oracle, etc.). When testing a Web-Application, we will need to validate the synchronization between the two access points (Client (Browser) <-> Server Side (Database).
Validate that the data displayed on the site is the one stored in the back-end server.
Validate that each column has a MAX input limit (Any value that exceeds this length will be rejected).
Validate that the DB tables can handle the boundary values that are retrieved from the client.
Verify the functionality of the DB stored procedures (Name, Parameters, output, syntax, etc.).
Validate that every user's operation will update the database values (Add, Delete, and Edit).
Validate that the user will not be affected when there is a DB error (Back-end side).
Validate that the user cannot access the DB without proper authentication.
Validate that the DB queries are executed without any failures.
Validate that each table has the correct foreign/Primary keys.
Validate that the DB server can handle negative numbers.
Validate the response time of the DB server.
All DB tables should include a short description.
Validate that the database structure contains the preliminary specifications (Tables, Columns, Stored-Procedures, Indexes, data types, flags, etc.).
Validate that the user data is committed only when the process is done (in any failure along the way, this data should be ignored).
Validate that the client interacts with the relevant database (the back-end site will host multiple databases).
Validate that the client cannot update the DB with the ‘Null’ value (any tables with a column that prohibits this value).
Validate that there are no synchronization issues when the client/servers are located in a different Time zone.