Skip to content

Result resolver feature branch #21457

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

Merged
merged 7 commits into from
Jun 21, 2023
Merged

Conversation

eleanorjboyd
Copy link
Member

fixes #21394

This is branch will serve as a feature branch for all changes related to
switching to the remote resolver.
This will include
- switching from using the testAdapter to parse the return data to now
using this new class resultResolver
- adding tests for all testAdapters, fixing for server and adding for
resultResolver
- moving sendCommand to a new file, out of the server, and getting
pytest to adopt it
- moving the server which send the test IDs to a new file and adopt it
for both pytest and unittest
- write tests for these two new files.
Created a testIdServer to handle the starting up of the testIdServer for
both unittest and pytest. This extracts the method to be in another file
and easy to test.
adds test coverage for `testExecutionAdapter.ts` and
`pytestExecutionAdapter.ts`.
This PR
- moves populateTestTree to utils
- adds tests for execution adapters (pytest and unittest)
- resultResolver tests
- workspaceTestAdapater tests
@eleanorjboyd eleanorjboyd self-assigned this Jun 20, 2023
@eleanorjboyd eleanorjboyd added debt Covers everything internal: CI, testing, refactoring of the codebase, etc. feature-request Request for new features or functionality and removed debt Covers everything internal: CI, testing, refactoring of the codebase, etc. labels Jun 20, 2023
@eleanorjboyd eleanorjboyd marked this pull request as ready for review June 20, 2023 20:01
@eleanorjboyd
Copy link
Member Author

this PR does not actually enable dynamic run results- it only setups up the resultResolver class which allows for dynamic to start happening. The actual PR to have the packages sent by the python server be dynamic will come after.

@brettcannon brettcannon removed their request for review June 20, 2023 23:17
@eleanorjboyd eleanorjboyd merged commit 0f23238 into main Jun 21, 2023
@eleanorjboyd eleanorjboyd deleted the resultResolver-feature-branch branch June 21, 2023 17:28
eleanorjboyd added a commit to eleanorjboyd/vscode-python that referenced this pull request Jun 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create TypeScript tests between Python code and VS Code
2 participants