Effective Test strategy-Technique-Methdology for high test coverage

First are some tips to create a good database test plan: 1. Database testing can get complex. It may be worth your while if you create a separate test plan specifically for database testing. 2. Look for database related requirements in your requirements documentation. You should specifically look for requirements related to  data migration  or database performance. A good source for eliciting database requirements is the database design documents. 3. You should plan for testing both the schema and the data. 4. Limit the scope of your database test. Your obvious focus should be on the important test items from a business point of view. For example, if your application is of a financial nature, data accuracy may be critical. If you application is a heavily used web application, the speed and concurrency of database transactions may be very important. 5. Your test environment should include a copy of the database. You may want to design your tests with a test database...

The GUI is in most cases given the most emphasis by the respective test managers as well as the development team members since the Graphical User Interface happens to be the most visible part of the application. However what is also important is to validate the information that can be considered as the heart of the application aka DATABASE. Let us consider a Banking application whereby a user makes transactions. Now from database testing viewpoint following things are important: The application stores the transaction information in the application database and displays them correctly to the user. No information is lost in the process. No partially performed or aborted operation information is saved by the application. No unauthorized individual is allowed to access the users information. To ensure all these above objectives, we need to use data validation or data testing. In this tutorial, we will study Difference Between GUI and Database Testing Types of Database Test...