Always defect detail should be very descriptive with proper step information and relevant attachments. Here is the list of ETL testing Best Practices which need to apply in defect logging.
The detail about the error must be reflected in both summary and description level. Add information’s about table name, job name, data flow stage (source to a stage, stage to target) where the job is failing and the issue.
Provide Test data
Share all test data used for testing the specific case, this will be useful to reproduce the defect as well as performing retesting.
Relevant SQL query
Always provide SQL query whatever used to catch the defect, don’t think that SQL query is available in screenshot which would make life harder.
We could use SQL query to insert/update/delete keep those query also in defect description.
Description at Depth
In the case of data mismatch, mention about the total count of source and target, then mention about deviation with reason.
When you find mismatch from MINUS query, don’t log the defect stating that these many records are not loaded from source to stage alone. Go little bit analysis and find the cause for the mismatch.
For example, you are noticing a table has the same count in staging and target but the data comparison minus query returns hundred records from stage to target.
The table has multiple columns we are not sure about problematic column at this stage.
Then find out an exact column which causes the mismatch and analyzes why those records alone not get loaded by using unique identifiers.
Now log the defect stating that “The column data are not loaded correctly into target table for unique identifiers“.
Provide details about job and command where exactly it gets failed along with a number of records processed and rejected.
If any dependent jobs need to be executed before running this job, provide that information also.
Don’t miss to upload proof
Upload screenshots whatever is required, for example, if you see a deviation in data type or length then upload images of both source and target table structure.
Attach related log files and bad file for reference.