Please enable JavaScript.

Coggle requires JavaScript to display documents.

2.5.3 3.5.3 (DATA INTEGRITY TESTING (Data integrity tests indicate…

- - - - the whole file is regularly checked in cycles, the CONTROL TECHNIQUE IS OFTEN REFERRED TO AS CYCLICAL CHECKING
  - - - Performed at the data element and record based levels.
      - Relational integrity is enforced through
        
        DATA VALIDATION ROUTINES built into the application
        
        or by DEFINING INPUT CONDITIONS CONSTRAINTS and DATA CHARACTERISTICS at the table definition in the database stage.
    - - Define existence relationships between ENTITIES IN DIFFERENT TABLES OF DATABASE that needs to be maintained by the DBMS
        
        required for maintaining interrelation integrity in the relational data model.
        
        Whenever two or more relations are related through referential constraints (primary and foreign key), it is necessary that references be kept consistent in the event of insertions, deletions and updates to these relations.
        
        Database software generally provides various built-in automated procedures for checking and ensuring referential integrity.
        
        Referential integrity checks involve ensuring that all references to a primary key from another table (i.e., a foreign key) actually exist in their original table
        
        nonpointer databases (e.g., relational), referential integrity checks involve making sure that all foreign keys exist in their original table
  - - - • Atomicity
        
        From a user perspective, a transaction is either completed in its entirety (i.e., all relevant database tables are updated) or not at all.
        
        If an error or interruption occurs, all changes made up to that point are backed out.
      - • Consistency
        
        All integrity conditions in the database are maintained with each transaction,
        
        taking the database from one consistent state into another consistent state.
      - • Isolation
        
        Each transaction is isolated from other transactions,
        
        so each transaction accesses only data that are part of a consistent database state.
      - • Durability
        
        If a transaction has been reported back to a user as complete,
        
        the resulting changes to the database survive subsequent hardware or software failures.
- - - - system defects
      - incomplete requirements designs, specifications
      - or errors in the test case itself
    - - Bottom up
        
        Testing begins with atomic units, such as programs or modules, and works upward until a complete system testing has taken place.
        
        advantages
        
        – There is no need for stubs or drivers.
        
        Stubs and Drivers are testing harness (dummy modules)
        
        – Testing can be started before all programs are complete.
        
        – Errors in critical modules are found early.
        
        Bottom up testing advantages
        
        Conduct and report test results
        
        Describe resources implied in testing, including personnel involved and information resources/facilities used during the test as well as actual versus expected test results.
        
        Results reported, along with the test plan, should be retained as part of the system’s permanent documentation.
        
        Address outstanding issues
        
        Identify errors and irregularities from the
        actual tests conducted.
        
        When such problems occur, the specific tests in question have to be redesigned in the test plan until acceptable conditions occur when the tests are redone.
      - Top Down
        
        Testing follows the opposite path, either in depth-first or
        breadth-first search order.
        
        The advantages follow:
        
        – Tests of major functions and processing are conducted early.
        
        – INTERFACE ERRORS CAN BE DETECTED SOONER .
        
        – Confidence in the system is increased because programmers and users actually see a working system.