Degenerate Dimension
Where will the Degenerate Dimension’s data stored?
November 22, 2017
the connection failed correct the database connection information and test the connection again
The connection failed correct the database connection information and test the connection again
November 29, 2017
Show all

Flat file target – Test scenarios

There are quite some situations which are environment specific when it comes to Flat File target validation. Here are some of them.

The common aspects to verify are:

  • File name
  • File Size and Format
  • File arrival, processing and deletion/archival times

The rest of the test cases are dependent on the way that is being generated. For example, if you take a case where the files need to be generated in a dynamic fashion with the name of the file containing the process name, operating unit and the timestamp at which it was generated.

Also, these dynamic target flat files should contain only specific data.

For example, if the files should be generated based on DEPT_ID 10,20,30 and each file should contain only it’s specific department’s data with the department name on the file.

File Name:

DEP_10_TIMESTAMP.txt

OR

DEPT_10_TIMESTAMP_INSERT.txt

OR

DEPT_10_TIMESTAMP_UPDATE.txt

In these specific requirements, along with the common flat file test cases, you have to consider the scenario specific test cases as well.

Last but not the least, the files generated are also based on the server’s timestamp and the default values. In the above case, if the logic uses database or Informatica’s server time to be applied to the filename then, you have to identify in which time zone the server is running and if the times are matching in all three environments like the QA/UAT and PROD.

Leave a Reply

Your email address will not be published. Required fields are marked *

Share
+1
Tweet
Pin
Share