-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
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
Add integration tests using WebdriverIO #2322
Comments
Thank you for raising this enhancement request. |
Test Plan:
|
vscode-extension-tester
vscode-extension-tester
Here are the branches I've created for my research - each branch contains a sample test that uses the given framework. WebdriverIO: test/wdio Link to research: https://ent.box.com/s/m32dgpfnt5bvwsiuvxr85kesvh3ty8mn |
vscode-extension-tester
Is your feature request related to a problem? Please describe.
Currently, our tests consist of unit tests and snapshots. We also have some Selenium tests for the Theia environment, but we don't have a set of integration tests for testing how the extension behaves within VS Code.
We might not be able to add these integration tests to our automated pipelines (as VS Code needs a display to show its UI), but it would help to run this locally when adding new features or addressing bugs to make sure that all features work as intended.
Describe the solution you'd like
Leverage the WebdriverIO framework to create a preliminary set of integration tests for Zowe Explorer.
Describe alternatives you've considered
I'm not aware of other frameworks for testing the user interface for VS Code extensions, but if an alternative exists, we should compare our options and pick the best framework for our use cases.
Tasks
The text was updated successfully, but these errors were encountered: