Clean up XUnitParser and add tests.#7263
Clean up XUnitParser and add tests.#7263ericsnowcurrently merged 30 commits intomicrosoft:masterfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## master #7263 +/- ##
==========================================
+ Coverage 57.82% 58.69% +0.87%
==========================================
Files 494 494
Lines 21475 21825 +350
Branches 3494 3498 +4
==========================================
+ Hits 12417 12811 +394
+ Misses 8267 8217 -50
- Partials 791 797 +6
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Can you rename helpers-declarative, helpers-nodes and helpers-results using camelCase? I'm also not sold on the idea of splitting the helpers in 4 different files 🤔 The unit test imports
import { createResults } from '../helpers-declarative';
import { TestItem } from '../helpers-nodes';
import { createEmptyResults } from '../helpers-results';so why not have all these methods (and the rest of the the helper methods) in the same spot?
|
As to the multiple "helpers-" files, there are several reasons:
|
32fbe09 to
0cbd266
Compare
kimadeline
left a comment
There was a problem hiding this comment.
Once you update how you structure your helpers-* files we good to go 👍
4b2dfe6 to
6cbd6a5
Compare
6cbd6a5 to
e1b7f84
Compare
eb37a5c to
2d46d6a
Compare
This is a precursor to the fix for (for #6990).
[ ] Has a news entry file (remember to thank yourself!)[ ] Has sufficient logging.[ ] Has telemetry for enhancements.[ ] Test plan is updated as appropriate[ ]package-lock.jsonhas been regenerated by runningnpm install(if dependencies have changed)[ ] The wiki is updated with any design decisions/details.