This article talks about how a tester can apply exploratory testing in a better way. We need to adapt to the situation and quickly have to increase the productivity right way. When a tester is getting into a project where it has been started a long ago and there is no proper documentation (Technical Specification Document (TSD)), also lack test cases documented. The below points will definitely help in this case,
Explore about Schema:
Get the data model and understand the tables and referential integrity. Request for high-level information about what type of data is handled in these ETL jobs.
Despite the lack of poor documentation at least we could get little information which will be the key for next step kick off.
Invest time to understand the Jobs:
Install the ETL tool and request access for all required repositories and folders. Open job one by one and understand about source table, transformations and target tables. Just create a simple mapping document with the information whatever you have got.
Before this step, you must have good knowledge on transformation types.
Going through Test cases:
Take a look at existing test cases, whatever is available. Two things will be useful for this activity,
- The knowledge level will increase
- We can identify the gap in existing test cases, what are the test cases to be added and improved?
Analysis on logged Defects:
Get access to defect tracking tool and have a glance at the history of defects logged. It would give you an idea of identifying what kind of defect logged across tables and which area need to be focused more?