Skip to content
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

UI Test Strategy #24

Closed
dschaefer opened this issue Feb 20, 2019 · 1 comment
Closed

UI Test Strategy #24

dschaefer opened this issue Feb 20, 2019 · 1 comment

Comments

@dschaefer
Copy link
Contributor

Now that we have an incoming Memory Browser that uses vscode's webview API and React, how do we test such a thing?

This would include unit testing the components, testing of the UI while mocking out the back end server (i.e. the extension), and end to end testing in vscode (if that's even possible?)

@jonahgraham
Copy link
Contributor

I expect the memory browser to be removed when https://github.com/eclipse-cdt-cloud/vscode-memory-inspector is fully working, so no point investing further in testing infra on this in cdt-gdb-vscode, that work should happen on vscode-memory-inspector

@jonahgraham jonahgraham closed this as not planned Won't fix, can't repro, duplicate, stale Jan 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants