This article talks about how better we can think and implement in order to meet the project timeline despite the delay in getting preconditions such as test data or schema to commence our test execution phase.
It can be overcome by implementing isolation testing from the initial stage of ETL testing process.
Proactive thinking creates groundwork to make the product into production as planned in any kind of situation.
My Own Experience:
I have come across the same kind of situation, in one of my projects during our test design phase itself we have been asking about the date for getting test data from the production environment.
We came to know that there will be the delay in getting the data due to various reasons like data masking etc.
At the same time, the top management was discussing to complete the test execution by having the short span of time with adding a number of resources.
The very first job I did after the discussion was, have raised a risk alarm with mitigation plans.
- Plan A – Start execution as planned if we get test data on time
- Plan B -> Build a dummy test data based on our test cases with the help of Business analyst and project team
Isolation Testing Implementation:
We started our focus on Plan B from the second day of project kickoff itself, we have made test data to cover all of our test cases. During this stage, we kept things in our mind as precaution steps,
Also, we had daily progress tracker and daily call with the project team to ensure are we doing right and to ensure the data integrity levels despite dummy data.
We were all set with test data, still, we haven’t received the actually masked data from the production team.
Then started our execution with these test data itself and found more defects, we closely worked with the development team and closed defects.
We gave the sign off to proceed the deployment into UAT environment with this limitation itself even stakeholders agreed with this.
There were no critical defects in UAT phase. The Plan B worked out well with great proper implementations.
Likewise, if we foresee any delay in getting schema or test data, we need not rely on them, do a brainstorm with the team and select alternative approach (isolation testing) and implement it which makes our life easy and makes time to market.
Also, refer – how to perform exploratory testing in ETL testing?