When performing database testing, you are concerned with verifying that your data is being stored by the system in the manner in which you expect, and in such a way that no errors are introduced to the data. This article will present some scenarios along with examples of database tests that might uncover design flaws that may result in data corruption, unauthorized data access, lack of data integrity across multiple tables, and lack of adequate transaction performance.
This article is intended for developers and testers who:
- Are familiar with the basic SQL commands (we won’t spend time explaining the SQL queries used in this article)
- May have done some database testing manually
- Have an interest in automating some of that testing
This article will first walk through setting up IBM® Rational® Functional Tester (RFT) to connect to a Java™ Database Connectivity (JDBC™) data source. Next you will walk through a sample application (complete with database defects), and then look at example tests you might automate for database testing.
Note: This article was written using RFT 6.1, Apache Tomcat 5.5.9, Java™ 2 Platform, Standard Edition (J2SE®) 5.0, Java™ 2 Runtime Environment, Standard Edition (JRE™) 5.0, and Hypersonic SQL (HSQLDB) 1.7.1.

 
 
Jameswoo