Creating a detailed stats table for capturing details on the execution of dq rules.

[vigneshwarrvenkat]

detailed stats table for capturing details on the execution of dq rules

Description

#55

Related Issue

#55

Motivation and Context

As of now, the stats table details are not sufficient to get detailed insights on the rules executed. This PR provides more details using a detailed stats table on the execution of all the rules in a relational format.

How Has This Been Tested?

The testing was done in local env with the sample data provided with this framework.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (a725aaa) to head (58189c7).

Additional details and impacted files

@@            Coverage Diff             @@
##              main       #80    +/-   ##
==========================================
  Coverage   100.00%   100.00%            
==========================================
  Files           22        22            
  Lines         1490      1809   +319     
==========================================
+ Hits          1490      1809   +319     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[asingamaneni]

Thanks for your contribution.