Table of Contents

Search

  1. Preface
  2. Introduction to Data Validation Option
  3. New Features and Behavior Changes
  4. Repositories
  5. XML Data Source
  6. Tests for XML Data Sources
  7. Connections
  8. Expressions
  9. Table Pairs
  10. Tests for Table Pairs
  11. Single-Table Constraints
  12. Tests for Single-Table Constraints
  13. Examples of Tests from Spreadsheets
  14. SQL Views
  15. Lookup Views
  16. Join Views
  17. Aggregate Views
  18. Business Intelligence and Reporting Tools Reports
  19. Dashboards
  20. DVOCmd Command Line Program
  21. Troubleshooting
  22. Datatype Reference
  23. Reporting Views
  24. Metadata Import Syntax
  25. Jasper Reports
  26. Glossary

Data Validation Option User Guide

Data Validation Option User Guide

Scenario 3 - Importing the Spreadsheet into DVO

Scenario 3 - Importing the Spreadsheet into DVO

  1. Open the DVO Navigator.
  2. Right click on the same Table Pair used to create the empty spreadsheet and select
    Generate Tests from Spreadsheet
    .
  3. Using the dialog, click the
    Browse
    button and open the spreadsheet that you just saved.
  4. The tests are imported and displayed in the dialog.
  5. If you import a LOT of tests (e.g. many dozens or hundreds), the import process can take some time (e.g. 30-60 seconds or even longer) as the import process validates each row of the spreadsheet and identifies any errors.
  6. These errors are highlighted in the import dialog with red/yellow icons.
  7. Red icons on the left indicate the test in that row has errors.
  8. Yellow icons on individual cells point out specific cells that require attention.
  9. Correct the errors found during the import. In the image above, the last 2 tests have errors in them that need to be addressed.
  10. You can add and remove tests using this dialog by clicking on the
    Add
    and
    Remove
    buttons on the right.
  11. This provides you with additional controls when correcting imported test definitions.
  12. Click
    Save
    to generate the tests. Inspect the generated tests to verify that tests imported correctly.
  13. Note that all tests imported will be added to the Table Pair, even IF, the Table Pair already contains tests with the same definitions. i.e. duplicate checking is not performed when creating the new tests from the spreadsheet metadata.
    Although, this is a very simple example to illustrate how to use the spreadsheet import functionality, the real power of this functionality is when many dozens or hundreds of tests are required, and basic spreadsheet capabilities such as copy/paste or simple string expressions can be used in the spreadsheet to quickly create large numbers of tests.