Scribd
Upload
210 views

ETL Testing Notes

The document discusses roles and responsibilities as an ETL tester with experience in Informatica and SQL Server/Oracle databases. It includes details on analyzing requirements, creating test cases and scenarios, running jobs to validate data movement from source to target, and performing validations like record counts, duplicates, referential integrity, and functional testing. Methods for testing different source and target combinations like files to database are provided. Key Informatica concepts like the workflow manager, logs, and transformations are covered. The document also discusses testing documentation, lifecycles, terms, and validations performed as an ETL tester.

Uploaded by

Thiru Pasupuleti
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
210 views

ETL Testing Notes

The document discusses roles and responsibilities as an ETL tester with experience in Informatica and SQL Server/Oracle databases. It includes details on analyzing requirements, creating test cases and scenarios, running jobs to validate data movement from source to target, and performing validations like record counts, duplicates, referential integrity, and functional testing. Methods for testing different source and target combinations like files to database are provided. Key Informatica concepts like the workflow manager, logs, and transformations are covered. The document also discusses testing documentation, lifecycles, terms, and validations performed as an ETL tester.

Uploaded by

Thiru Pasupuleti
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

1. Brief about you self ?

My self ----- having ---- years of experience in Testing in which –-- years in to ETL testing. Coming to
the tools I have experience in Informatica/Informatica cloud and the databases are Oracle and SQL
server.

2. Roles and Responsibilities:


 Currently we are working on Agile methodology which we have 2 weeks a sprint. Once the
sprint planning is done will be assigned few of the user stories.
 Once I get user stories, I will be analyzing the requirements and preparing test
scenarios/Test cases and will be preparing queries based on Mapping document.
 Once the code has been deployed for testing, I will be running the jobs and validating the
data from source to target.
3. What are all the validations you perform?
 Record count validations
 Duplicate Check
 Reconciliation (Entire data validation from Source to target)
 Referential integrity Checks
 Any other functional scenarios that need to be validated.
4. What is your source and what is your target?
 Here you can say I have worked on multiple projects where we have
o Source and target is same Database
o Source is flat files and target is database
o Source is combination of Files and database and target is DB

Note : Here you can stick to one database where you have good Knowledge like SQL serve/Oracle

5. When source is File and target is Database how you are validating data?
 We have some informatica jobs which we can load that file in to temporary tables.
 And once we load the files in to tables, we will be writing Source query based on
STTM(Source Target Mapping document ) and we will compare with target data.
6. How do you compare if you have source and target is different database?
 If we have source and target has different database we can do below
o We can verify if we have DB connections available between 2 different databases
o We should use some automation tool that we can test using that ( exp: python)
o We can compare sample data in excel (This is not recommended )
7. Informatica where we can run the jobs?
 We can Run the jobs in work flow manager.
8. Informatica where we can See the logs?
 We can see the log file in work flow monitor.
9. What are all some transformations available in Informatica ?
 Source qualifier
 Lookup
 Joiner
 Filter
 Aggregate
 Expression
10. Do you Run the jobs in informatica?
 Some Projects yes in some projects we don’t have access where we can run from Control M
11. Are you providing estimates for the User stories?
 If below 4 years of experience you can tell you Lead will take care
 If you have more than 4 years tell that will be giving story points for the User stories which
are assigned to me
 1 story point=7 Hours
 Tell that you are not using any approach we are giving based on the complexity.
12. Remember the below terms in Agile
 Backlog
 User story
 Product owner
 Scrum master
 Story points
 Demo

Note : You can refer to my class where I have explained each of the terms.

13. What is the defect life cycle?


 New  Open Or Reject  In Analysis  In Development  Ready to test  In Test done
or Re Open.
14. Which test management tool you have experience?
 JIRA
15. Few documents you get while Testing?
 Test Plan: Manager/Lead is responsible to create it contains in scope , out of scope, project
time lines, Like System testing/ System Integration Testing.
 Test Strategy: Manager/Lead is responsible to create which contains how we are going to
perform testing like cycles planned and when we are executing what.
 RTM: Requirement Trackability Metrix where you can map your test scenarios/Test cases
against the requirements to make sure you are covering all the testing.
 BRD : Business Analyst will create the documents this helps to create the test
scenarios/Cases
 FRD : Business Analyst will create the documents this helps to create the test
scenarios/Cases
 STTM : Business Analyst will create the documents this helps to create the Source queries.
16. Testing Life cycle ?
 Require Phase
 Analysis Phase
 Test preparation
 Test Execution
o System Testing
o System Integration Testing
o User Acceptance Testing
 Sign off
17. Below Terms needs to be clear
 Dimension Table
 Fact table
 Star/Snow Flake Schema
 OLAP vs OLTP
 Types of dimensions
 Types of Facts
 Slowly Changing Dimensions (SCD)
18. What is the Architecture of your project ?
 Currently we are getting data from multiple sources ( files /database ) from there data will
be loading in to staging area from the transformations rules will apply and load in to target
tables .

Source Staging Datawarehouse

19. What is the use of Staging Area ?


 It is used to combine the data which we are getting from multiple sources and while loading
data to staging tables data cleansing will happen ( means any unwanted data can be rejected
and data can be format in to uniform format)
20. Below Testing Terms needs to Remember
 Regression testing : This testing is done to make sure that new code changes should not
have side effects on the existing functionalities. It ensures that the old code still works once
the latest code changes are done.
 Re testing : Re-testing is carried out to confirm the test cases that failed in the final
execution are passing after the defects are fixed
 Smoke Testing: is a software testing process that determines whether the deployed
software build is stable or not. Smoke testing is a confirmation for QA team to proceed with
further software testing.
 Sanity Testing : is a subset of regression testing. Sanity testing is performed to ensure that
the code changes that are made are working as properly. Sanity testing is a stoppage to
check whether testing for the build can proceed or not.

You might also like