7/30/2019 DW Projects

1/6

Project Name

What were the main risk & challenges you faced

and how did MindTree or project team

overcome them

Test cases

What was the test methodology followed for

ETL & BI Testing

What kind of metrics were collected

7/30/2019 DW Projects

2/6

FAS91 Upgrade (Financial accounting standards-US)

The test execution was in line with the SDLC process on the project.

The different areas of testing included application testing, warehouse(DART) to

downstream application(FAS91) testing(Dart staging to application

staging),Outbound testing-(FAS91 to PSGL-Data validation)

Some of the DW standards that we have tested includes:Slowly changing dimensions

Fact tables testing

Transactional tables with aggregations

Data cleansing with the reject handling process in place

Exceptions validations of ETL.

The tools used are SQL developer (PL/SQL)

Most of the metrics were collected from QC for tracking the testing progress.

On completion of testing the main reports were "Test coverage", "Test Plan report"

and "Test Execution report".

These report give the test cases created for the project, the final status of the test

cases of these test cases executed and the coverage w.r.t these test cases.

The complexity here was incorporating the constant design changes because of

instable vendor product(Prematics) where we have come up with generic queries

which have been packaged(Automation using PL/SQL scripts) where any change in

furthur change in ETL were easily handled. The Mock up data has been updated in

the staging table as per the scenarios which was a tedious task as the data provided

by the client was in adequate.

850 test cases have been created out of which 425 have been automated.

7/30/2019 DW Projects

3/6

Project Name

What were the main risk & challenges

you faced and how did MindTree or

project team overcome them

Test cases

What was the test methodologyfollowed for ETL & BI Testing

What kind of metrics were collected

7/30/2019 DW Projects

4/6

DW Platform upgrade(Database migration)

The test execution was in line with the SDLC process on the project.

The different areas of testing included Source(Dart 9i) and Target (Dart 11g)mapping

and Transformation validations(objects are like Tables, Views, Stored procedure,

Permission , Grants, Supplement logs and Partition are checked between 9i - 11g)Some of the DW standards that we have tested includes:

Transactional tables with aggregations

Data cleansing with the reject handling process in place

Exceptions validations of ETL.

The tools used are Sql data examiner

Most of the metrics were collected from QC for tracking the testing progress.

On completion of testing the main reports were "Test coverage", "Test Plan report"

and "Test Execution report".

These report give the test cases created for the project, the final status of the test

cases of these test cases executed and the coverage w.r.t these test cases. There were

around 40 generic test cases created apart from that the test cases covered buy the

tool were 9000(Total number of tables to be tested in DART = 3000 ( assumption 50

tables per Schema)>Total number of check points needs to tested in each table =

Schema, Objects , Data (A-B) and (B-C)>Total manual cases to be executed = 3000* 3

(Minimum Check points) = 9000 units

No clarity on the requirements only the Migration from 9i to 11 g was quoted. We had

examined lot of options where huge effort was put to arrive at the test strategy andfinally decided on the Sql data examiner which was provided great values to client in

terms of Effort & Cost.

20 generic test cases(QC) and 9000 using the tool.

7/30/2019 DW Projects

5/6

UBS

Project Name

What were the main risk & challenges you faced and how

did MindTree or project team overcome them

What was the test methodology followed for ETL & BI

Testing

What kind of metrics were collected

7/30/2019 DW Projects

6/6

UBS(Universal banking system which is FLEXCUBE)

The test execution was in line with the SDLC process on the project.

The different areas of testing included Upstream application testing, upstream to

warehouse interfaces, warehouse to downstream interfaces and downstream applicationtesting. Apart from this, business reports created form the universes and warehouse were

also tested. [BIF team in SVB].

Some of the DW standards that we have tested includes:

Slowly changing dimensions

Fact tables testing

Transactional tables with aggregations

Data cleansing with the reject handling process in place

Exceptions validations of ETL.

The tools used are SQL developer and Toad for Oracle and Beyond compare and MS excel

for data validation.

A lot of complex SQL queries were created for validating the data.

Most of the metrics were collected from QC for tracking the testing progress.

On completion of testing the main reports were "Test coverage", "Test Plan report" and

"Test Execution report".

These report give the test cases created for the project, the final status of the test cases of

these test cases executed and the coverage w.r.t these test cases.

Non QC reports included the data extracts of validations.

Downstream testing was the main challenge and we overcame this with the help of the

application support engineers as that team was also from MindTree