The primary aim of the data cycle test is not to trace functional defects in individual functions, but to find integration defects. The test focuses on the link between various functions and the way in which they deal with communal data. The DCyT is most effective if the functionality of the individual functions has already been sufficiently tested. The most important test basis is the CRUD matrix and a description of the applicable integrity rules. If this matrix is not present, it must be created to enable the drafting of the test design within the framework of the data cycle test. The following checklist can be used to check the test basis for the data cycle test:
• Is a CRUD matrix present?
• Can every entity be entered, viewed, changed, and deleted?
• Is it clear in which function(s) an entity can be entered, viewed, changed, or deleted?
• Are all entities described?
• Is there an entity diagram (Entity Relationship Diagram, ERD)?
• Have the relationships between the various entities been described?
• Have the referential relation checks for the relations been described?
• Is a CRUD matrix present?
• Can every entity be entered, viewed, changed, and deleted?
• Is it clear in which function(s) an entity can be entered, viewed, changed, or deleted?
• Are all entities described?
• Is there an entity diagram (Entity Relationship Diagram, ERD)?
• Have the relationships between the various entities been described?
• Have the referential relation checks for the relations been described?
0 comments:
Post a Comment