The document discusses test automation for database solutions with a focus on two complementary approaches: single functionality testing and end-to-end testing. It outlines various examples of how each testing method works in practice, highlighting different checks and verifications performed on database tables. Additionally, it touches on the implementation of continuous integration processes related to these testing methods.

1. © 2013 Acxiom Corporation. All Rights Reserved. © 2013 Acxiom Corporation. All Rights Reserved.
Paweł Gutowski
Test Automation
for Database Solutions
2015-09-04

2. © 2013 Acxiom Corporation. All Rights Reserved.
Agenda
• Acxiom
• Why 2 complementary approaches to test automation?
• Single functionality testing
• End 2 End testing
• Continuous integration
• Questions

3. © 2013 Acxiom Corporation. All Rights Reserved.
Acxiom
Why does data matter?

4. © 2013 Acxiom Corporation. All Rights Reserved.
Why 2 complementary approaches to test
automation?
Solution that needed test coverage (dummy below is much smaller but should give an idea what is our product)

5. © 2013 Acxiom Corporation. All Rights Reserved.
Single Functionality Test Automation

6. © 2013 Acxiom Corporation. All Rights Reserved.
Single Functionality Test Automation
6

7. © 2013 Acxiom Corporation. All Rights Reserved.
Single Functionality Test Automation
Audits:
Check if there is any difference between tables (actual vs expected result)
Example: Full outer join on 2 tables checking if any field is different between them
Check if created table has correct columns (or check any other characteristic)
Example: Run query against system views (or catalogue views etc) that verify the structure
7

8. © 2013 Acxiom Corporation. All Rights Reserved.
Single Functionality Test Automation

9. © 2013 Acxiom Corporation. All Rights Reserved.
End 2 End Test Automation

10. © 2013 Acxiom Corporation. All Rights Reserved.
End 2 End Test Automation

11. © 2013 Acxiom Corporation. All Rights Reserved.
End 2 End Test Automation

12. © 2013 Acxiom Corporation. All Rights Reserved.
End 2 End Test Automation
Example 1
Check if there are any records in BUSINESS TABLE1 that would have Country Code null.
Example 2
Check that if record in BUSINESS TABLE1 has been marked as high quality, it must have
consumer link associated with it in BUSINESS TABLE2
Example 3
Check that values in name_hash field are created the same way for all the records, by applying
concatenation on 3 fields coming directly from source file and hashing the result.
Example 4
Check that all IDs from BUSINESS TABLE1 can be found in BUSINESS TABLE2 as well. The
reverse should happen as well, but only if rehygiene process has not be run.
12

13. © 2013 Acxiom Corporation. All Rights Reserved.
End 2 End Test Automation
Example5
Field in BUSINESS TABLE1 should be mapped using 3rd party response (if not null)
Otherwise it should be taken from BUSINESS TABLE2 (if not null)
Otherwise, „DEFAULT” value should be set
SELECT COUNT(1) FROM (
<?perl
... Use oracle system view to get list of all 3rd party response tables
... Union them all together
?>)
JOIN -> 2 business tables
WHERE -> business condition is broken
Expected result = 0
Example 6
Verify that if data comes again for existing record but with better priority, it will update existing records. But lower priority should not make
an update
SELECT COUNT(1) FROM
JOIN -> 3 tables („before”, „incoming data”, „after”)
WHERE -> tested condition
13

14. © 2013 Acxiom Corporation. All Rights Reserved.
End 2 End Test Automation
14

15. © 2013 Acxiom Corporation. All Rights Reserved.
Continuous integration
Almost there 
• Nightly: End 2 End
• Commit based: Single Functionality (as an addition to unit tests)

16. 16