Adding tasks for publishing results #695
Conversation
|
|
|
LGTM 👍 |
|
@hemal7735 Sure. I have added the screenshot in the description. Can we requeue the travis CI integration? |
|
@evenstensberg Can we requeue the travis CI? There seems no evident reason why this would fail. |
|
@vagisha-nidhi the commit message doesn't follow the pattern, that's why the CI is failing. https://github.com/webpack/webpack-cli/blob/master/CONTRIBUTING.md#commit-message-format-1 If you can rewrite your message, it would be great. If you can't, it's not a problem, we can rewrite the commit message when you we will merge your PR into master! :) |
There was a problem hiding this comment.
LGTM 👍
P.S.(off topic) I joined DTU B.Tech IT this year (you are too from DTU). Any ideas what should I do this winter @vagisha-nidhi?
webpack-bot
added
PR: review-outdated
and removed
PR: conflict
PR: reviewed-approved
labels
|
@vagisha-nidhi Thanks for your update. I labeled the Pull Request so reviewers will review it again. @dhruvdutt Please review the new changes. |
|
Do you have a link of this working atm? Can't seem to find it |
|
On master branch is there, "Tests" tab |
|
For each PR here |
What kind of change does this PR introduce?
This PR is related to the issue #694
The PR helps to publish test results for reporting in Azure Pipelines.
Did you add tests for your changes?
No
If relevant, did you update the documentation?
Summary
Azure Pipelines provides excellent reporting capabilities that can be leveraged by this PR.
An example report is shown in the image below.
A screenshot for code coverage :
Does this PR introduce a breaking change?
No
Other information