-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Need for non-UI end-to-end testing #2919
Comments
Can't you just try to make it work and then we see how we can extract general parts if it's worth it? |
I tried a little bit and hit some road bumps, so I wanted to see if any of you saw any reason why this would be a bad idea, before going further. |
I did some integration non UI testings for the fontend modules of theia extensions (no backend modules).
For my initial use case this method was enough but I guess that in time there will be more of them. I used jest-puppeteer to execute code in the browser context in my tests. So the test code looks somewhat like this:
If this mechanism is desired inside theia I can create a PR. |
As far as I understand yes. But I didn't get into it yet. |
Closed in #6852 :) |
I recently wanted to make an end-to-end test involving Theia and clangd, to verify that some actions in the frontend (changing build configuration) worked correctly with clangd and that the system as a whole gave good results.
The only way right now is to do a UI test, where you simulate clicks in a Theia application. However, there is nothing in this test that inherently needs to be UI-driven. We only need some non-UI components of the frontend, a backend, and clangd.
I think it would be nice to be able to run tests where we instantiate some non-UI components of the frontend (including the bits necessary to connect to a backend) and drive the test from a standard mocha test file.
The text was updated successfully, but these errors were encountered: