Software system testing and quality assurance
Software system testing and quality assurance
Formal techniques for data base design
Formal techniques for data base design
Automating code and documentation and management (CDM): the intelligent guidance of change
Automating code and documentation and management (CDM): the intelligent guidance of change
Comparing the Effectiveness of Software Testing Strategies
IEEE Transactions on Software Engineering
The complete guide to software testing
The complete guide to software testing
A case study in test environment evolution
ACM SIGSOFT Software Engineering Notes
The growth of software testing
Communications of the ACM
Testing the Completeness of Specifications
IEEE Transactions on Software Engineering
The Data Model Compiler: a tool for generating object-oriented database systems
OODS '86 Proceedings on the 1986 international workshop on Object-oriented database systems
The entity-relationship model—toward a unified view of data
ACM Transactions on Database Systems (TODS) - Special issue: papers from the international conference on very large data bases: September 22–24, 1975, Framingham, MA
Using a Meta Model to Represent Object-Oriented Data Models
Proceedings of the Sixth International Conference on Data Engineering
Characterization of Well-Behaved Database Schemata and Their Update Semantics
VLDB '83 Proceedings of the 9th International Conference on Very Large Data Bases
Verification and Testing of S-ER Representations
ER '81 Proceedings of the Second International Conference on the Entity-Relationship Approach to Information Modeling and Analysis
Toward a theory of test data selection
IEEE Transactions on Software Engineering
| Hi-index | 0.00 |
As database applications become larger and more complex, the development of suitable test plans to assure robust and reliable software becomes essential. The testing procedure must establish the applications reliability from the human expectation viewpoint as well as its correctness and robustness.The predetermined goals of this testing procedure are to assure high reliability of the application and ascertain that the software performed according to specifications, while remaining within the project's time and budgetary constraints. Errors identified during development can be corrected with minimal cost when compared to errors uncovered by users after the software release. By overlapping testing with development, and automating the production of a standardized set of test plans, the incremental production time can be minimized. By generating an application specific test plan, syntactic and semantic specifications of the actual system applications can be tested. A side effect of this specific, interleaved correctness testing is the uncovering of user interface inconsistencies and their refinement before exposure of the application to the real end user.Analysis of the results of our experimental testing showed the keystone to be the test plan. Since the completeness and veracity of this document is a prime determining factor in the validity of the testing, we have developed program using C++ on a Sun workstation to automatically generate test plans from the design schema.This paper presents an automated/manual testing scheme suitable for assuring the validity of large database applications. The initial premises, design execution and consequences of the test procedure is detailed followed by a description of the automation of strategic components.