redhat-developer / redhat-developer/vscode-extension-tester
Running E2E tests that rely on mocking certain logic
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 326
- Forks
- 88
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 71
Description
Hi all,
I am in need of running E2E tests for an extension. However this extension depends on several external calls that are made when interacting with the UI (eg: Certain UIs are only loaded if the user is logged in and the login is handled via external calls). Unfortunately, these calls cannot be made in the test environment and they need to be mocked for testing purposes. Is there a way that we can integrate the concept of mocking in the same test environment so that we can test the UI from end to end.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing the existing end-to-end test environment and how external calls are handled, then define how mocking should integrate so UI flows depending on login or other external calls can be exercised; done means those flows run without unavailable test-environment calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100