Software Testing Methods

Part:   1  2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17   18  19  20  21  22  23  24  25  26  27  28 

(Continued from previous part...)

Query reaponse time
The turnaround time for responding to queries in a database must be short; therefor, query response time is essential for online transactions. The results from this test will help to identify problems, such as possible bottlenecks in the network, sspecific queries, the database structure, or the hardware.

Data integrity
Data stored in the database should include such items as the catalog, pricing, shipping tables, tax tables, order database, and customer information. Testng must verify the integrity of the stored data. Testing should be done on a regular basis because data changes over time.

Data integrity tests

Data integrity can be tested as follows to ensure that the data is valid and not corrupt:

Test the creation, modification, and deletion of data in tables as specified in the business requirement.

Test to make sure that sets of radio buttons represent a fixed set of values. You should also check for NULL or EMPTY values.

Test to make sure that data is save to the database and that each values gets saved fully. You should watch for the truncation of strings and that numeric values are not rounded off.

Test to make sure that default values are stored and saved.

Test the compatibility with old data. You should ensure that all updates do not affect the data you have on file in your database.

Data validity
The most common data errors are due to incorrect data entry, called data validity errors.

Recovery testing

• The system recovers from faukts and resumes processing within a predefined period of time.
• The system is fault-tolerant, which means that processing faults do not halt the overall functioning of the system.
• Data recovery and restart are correct in case of automatic recovery. If recovery requires human intervention, the mean time to repair the database is within predefined acceptable limits.

When testing a SQL server

• If the Web site publishes from inside the SQL Server straight to a Web page, is the data accurate and of the correct data type?
• If the SQL Server reads from a stored procedure to produce a Web page or if the stored procedure is changed, does the data on the page change?
• If you are using FrontPage or interDev is the data connection to your pages secure?
• Does the database have scheduled maintenance with a log so testers can set changes or errors?
• Can the tester check to see how back ups are being handled?
• Is the database secure?

(Continued on next part...)

Part:   1  2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17   18  19  20  21  22  23  24  25  26  27  28