Editor's Note: This article is written by Jenny Richards of RemoteDBA.com, a leader in remote database admin services.
Part of every software application today is database testing, since virtually everything must have a database at the backend to work. There’s a database behind every desktop, web, peer-to-peer, enterprise, client server or individual application in healthcare, finance, retail or mailing.
As applications become more complex, it becomes necessary to have stronger and more secure databases. In addition, for applications that have high transaction frequencies, it is necessary to have fully featured DB tools, of which there are several in the market today. They all differ in robustness, cost, security and features, with their unique up and downsides.
However, all applications will base on one DB tool or other. DB tools facilitate CRUD operations, described as:
- CREATE – A create operation occurs when a user saves a new transaction
- RETRIEVE – A Retrieve operation happens when a user views or searches from saved transactions
- UPDATE – An update transaction takes place when a user modifies or edits an existing transaction/record
- DELETE – A delete operation occurs when a user removes existing records from the database
The tool used and how operations are carried out is not important for users because invariably, all user operations for all tools boil down to one of the above transactions.
What should be tested?
Database testers are responsible for the following database testing activities: