Have both field coverage diff and field coverage #51
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.
Addressing my concerns in #46 , now we have both coverage and fields with >5% difference in coverage.
That's coverage. I don't know about the correct name so I made it as precise as possible - we get this coverage from dividing job stats on total items.
![Screenshot 2019-04-09 at 13 22 37](https://user-images.githubusercontent.com/10396557/55821046-8ef7aa00-5aca-11e9-88f4-20293cf68751.png)
![Screenshot 2019-04-09 at 13 23 46](https://user-images.githubusercontent.com/10396557/55821123-b9e1fe00-5aca-11e9-9803-4af26b3fffcf.png)
And that's the >5% difference (from substraction of values from the previous graph)
That's how it looks with % tickformat, which is an option, not included in this pr
![Screenshot 2019-04-09 at 13 33 31](https://user-images.githubusercontent.com/10396557/55821733-26113180-5acc-11e9-957a-08a53942fe9d.png)
That's how it looks on unbalanced data (>100% coverage)
![Screenshot 2019-04-09 at 13 35 24](https://user-images.githubusercontent.com/10396557/55821823-58bb2a00-5acc-11e9-85b8-2fc4a3ce43c0.png)