vscode-test related updates #2695
Conversation
|
Adding @bpasero for review, since he was the original author of this. |
| | `CODE_LOCALE` | Display language to use when running the tests (default is English) | | ||
| | `CODE_DISABLE_EXTENSIONS` | Disable all other extensions except the one that is being tested | | ||
| | `CODE_TESTS_DATA_DIR` | Allows to specify the user-data-dir for the tests to use and thus enables to run multiple tests at the same time | | ||
| Extension tests can be run on CI services. The `vscode-test` repository itself contains a sample extension that is tested on Azure Devops Pipelines. You can check out the [build pipeline](https://dev.azure.com/vscode/VSCode/_build?definitionId=14) or jump directly to the [build definition yaml file](https://github.com/microsoft/vscode-test/blob/master/azure-pipelines.yml). |
There was a problem hiding this comment.
I've created a different public Azure DevOps project for this: https://dev.azure.com/vscode/vscode-test. Let's move the microsoft.vscode-test pipeline out of the VSCode project.
There was a problem hiding this comment.
I don't seem to have permission
There was a problem hiding this comment.
Updated. Give it another try.
There was a problem hiding this comment.
@octref I am a little bit confused about the impact of this change. I assume that yo code will still setup everything needed to run integration tests for the extension, so in most cases a user will not have to deal with vscode-test directly, unless maybe certain parameters are being changed. Under the hood, the generator will configure and use vscode-test accordingly.
If that assumption holds true, then I think the Overview section of Testing Extension should call that out very explicitly and provide a guide how to run extension tests when using having a generated extension. I think you are currently linking to the "Getting Started" section for extensions, but that one as far as I can tell does not mention running tests at all.
As such, I would split the document testing-extensions.md up into a basic and maybe advanced section. Does that make sense?
Good point. I realized most people would either use
|
See context at microsoft/vscode#71048.
@joaomoreno Please take a look at the release notes, testing/CI docs and see if it makes sense for you. I think it looks simpler.