I would expect the junit output to be consistent and helpful to finding which .vue component has linting issues.
Secondary gripe: I would also expect a -o option to output to a file. Output redirection is a pain here because if the tests fail then invalud XML (plain text) is generated.
What is actually happening?
The vue-cli-service lint command creates unhelpful output in junit format. In particular the fact that the name attribzte of a failed testcase is not set to the path is very confusing especially to Azure Devops Pipelines which parse the test results. They show the name attribute and for failed tests this is the eslint rule name. So you see "org.eslint.no-trailing-spaces" but have no idea where that rule was broken.
For passed tests the name attribute is the path to the component - this should always be the case.
Version
4.4.6
Environment info
Steps to reproduce
npx vue-cli-service lint --max-warnings 0 --no-fix --silent --format junit > junit.xml
What is expected?
I would expect the junit output to be consistent and helpful to finding which .vue component has linting issues.
Secondary gripe: I would also expect a -o option to output to a file. Output redirection is a pain here because if the tests fail then invalud XML (plain text) is generated.
What is actually happening?
The vue-cli-service lint command creates unhelpful output in junit format. In particular the fact that the name attribzte of a failed testcase is not set to the path is very confusing especially to Azure Devops Pipelines which parse the test results. They show the name attribute and for failed tests this is the eslint rule name. So you see "org.eslint.no-trailing-spaces" but have no idea where that rule was broken.
For passed tests the name attribute is the path to the component - this should always be the case.