We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I was trying to understand VSCode code structure and testing philosophy, and tried to get code coverage on Linux according to the instructions:
https://github.com/microsoft/vscode/blob/main/test/unit/README.md#os-x-and-linux
I got here by following the links in Wiki:
Writing Tests -> Unit Tests (in the sentence "Tests can be run manually on the command line, see the instructions here.")
However I got empty coverage result. It seems that test.sh does not have any logic around handling the --coverage flag.
test.sh
--coverage
My guess is that the instructions are outdated, and manual coverage collection requires a different process?
Does this issue occur when all extensions are disabled?: N/A
67a68e1
Steps to Reproduce:
./scripts/test.sh --coverage
./build/coverage/index.html
The text was updated successfully, but these errors were encountered:
connor4312
No branches or pull requests
I was trying to understand VSCode code structure and testing philosophy, and tried to get code coverage on Linux according to the instructions:
https://github.com/microsoft/vscode/blob/main/test/unit/README.md#os-x-and-linux
I got here by following the links in Wiki:
Writing Tests -> Unit Tests (in the sentence "Tests can be run manually on the command line, see the instructions here.")
However I got empty coverage result. It seems that
test.sh
does not have any logic around handling the--coverage
flag.My guess is that the instructions are outdated, and manual coverage collection requires a different process?
Does this issue occur when all extensions are disabled?: N/A
67a68e1
Steps to Reproduce:
./scripts/test.sh --coverage
./build/coverage/index.html
The text was updated successfully, but these errors were encountered: