The document outlines the use of an ETL Validator for checking mandatory fields in a database, specifically focusing on the customers table. It details the steps for creating test cases to identify records with blank fields and null values, including SQL query rules and generating reports. Key benefits of using ETL Validator include comprehensive test coverage, repeatability, cost reduction, and faster time to market.

1. ETL Validator Usecases
Mandatory Field Check
www.datagaps.com

2. ETL Validator
Comprehensive Testing
Automation
Extract. Load. Validate (Patented)

3. 100% Test
Coverage
Repeatability Cost Reduction Faster Time to
Market
End to End Testing
ETL Validator
Key Benefits

4. Usecase :
Checking for mandatory fields
Create a test case:
Identify records from
Customers table with
• ‘First Name’ is blank
• ‘Marital Status’is null
Start with creating a
new Data Rules Test
Plan

5. Usecase:
Checking for mandatory fields
Name your test plan.
Select the Database
Connection.
Navigate to the next
screen.

6. Usecase:
Checking for mandatory fields
Expand the schema; in
this example, ‘public’.
Select and expand the
table ‘Customers’.
Select the field
‘cust_first_name’.
Click on ‘Add SQL Query
Rule’.

7. Usecase:
Checking for mandatory fields
Type in the SQL query:
select * from customers
where cust_first_name = ‘’
‘Run Query’ to see the
results.
Name the query.
Save the query.

8. Usecase:
Checking for mandatory fields
Add second condition:
flag records where
Marital Status is null.
Select the field
‘cust_marital_status’
Click on ‘Add New Rule’.
Choose ‘is not null’; the
test case will flag those
records that do not
satisfy the rule.

9. Usecase:
Checking for mandatory fields
Click on ‘Test’.
Records that do not
satisfy the rule will be
displayed in grid below.
Navigate to Next
Screen.

10. Usecase:
Checking for mandatory fields
In order to run test cases
of only the ‘Customers’
table –
• Click on settings icon
• Unselect other tables.

11. Usecase:
Checking for mandatory fields
Click on ‘Run’.
‘FAILED’ indicates that
there are records that
didn’t satisfy the rule.
The grid shows results
from first test case in the
list above.
Click on subsequent rows
to see those results.
Click on ‘View Report in
Browser’ to see same
results in web layout.

12. Usecase:
Checking for mandatory fields
Same info is displayed
in web layout.
The link can be shared
with others.
Click on the upward
arrow to see the
records

13. More with ETL Validator….
• Data counts validation with allowed variance
• Check Data Quality using Data Rules Test Plan
• Advanced ETL Testing using a Component Test Case
• Avoiding inline views on your queries in ETL Validator
www.datagaps.com