Add testing to contribution detail report, covering dev/core/issues#170 #12281
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR restructures the contribution detail report to bring it under testing. It re-fixes issue 170 in a more solid tested way
Before
Report toxic & untested
After
Report less toxic & brought under testing
Technical Details
The beginPostProcessCommon function is called by unit tests / the reporttemplates.get api while postProcess is not. We remove the postProcess function & rely on the parent, moving report-specific stuff to beginPostProcessCommon
Comments
@lcdservices am hoping you can give the report a thorough review once tests pass. Can now extend this with tests for any issues found