Data and Database Integrity Testing
[The databases and the database processes should be tested as a subsystem within the <Project Name>. These subsystems should be tested without the target-of-test’s User Interface as the interface to the data. Additional research into the DataBase Management System (DBMS) needs to be performed to identify the tools and techniques that may exist to support the testing identified below.]
| Test Objective: | [Ensure database access methods and processes function properly and without data corruption.] |
| Technique: | · [Invoke each database access method and process, seeding each with valid and invalid data or requests for data. · Inspect the database to ensure the data has been populated as intended, all database events occurred properly, or review the returned data to ensure that the correct data was retrieved for the correct reasons] |
| Completion Criteria: | [All database access methods and processes function as designed and without any data corruption.] |
| Special Considerations: | · [Testing may require a DBMS development environment or drivers to enter or modify data directly in the databases. · Processes should be invoked manually. · Small or minimally sized databases (limited number of records) should be used to increase the visibility of any non-acceptable events.] |
Function Testing
[Function testing of the target-of-test should focus on any requirements for test that can be traced directly to use cases or business functions and business rules. The goals of these tests are to verify proper data acceptance, processing, and retrieval, and the appropriate implementation of the business rules. This type of testing is based upon black box techniques; that is verifying the application and its internal processes by interacting with the application via the Graphical User Interface (GUI) and analyzing the output or results. Identified below is an outline of the testing recommended for each application:]
| Test Objective: | [Ensure proper target-of-test functionality, including navigation, data entry, processing, and retrieval.] |
| Technique: | [Execute each use case, use-case flow, or function, using valid and invalid data, to verify the following: · The expected results occur when valid data is used. · The appropriate error or warning messages are displayed when invalid data is used. · Each business rule is properly applied.] |
| Completion Criteria: | · [All planned tests have been executed. · All identified defects have been addressed.] |
| Special Considerations: | [Identify or describe those items or issues (internal or external) that impact the implementation and execution of function test] |
Дата добавления: 2015-12-17; просмотров: 16; Мы поможем в написании вашей работы! |
Мы поможем в написании ваших работ!