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

Add dynamic results to testing rewrite #21462

Conversation

eleanorjboyd
Copy link
Member

fixes #21148 to add dynamic run results to the testing rewrite.

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 added feature-request Request for new features or functionality area-testing labels Jun 21, 2023
@eleanorjboyd eleanorjboyd self-assigned this Jun 21, 2023
@eleanorjboyd eleanorjboyd changed the title Add dynamic result Add dynamic results to testing rewrite Jun 21, 2023
@eleanorjboyd eleanorjboyd changed the base branch from main to resultResolver-feature-branch June 21, 2023 16:06
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.
This PR
- moves populateTestTree to utils
- adds tests for execution adapters (pytest and unittest)
- resultResolver tests
- workspaceTestAdapater tests
@eleanorjboyd eleanorjboyd added the skip tests Updates to tests unnecessary label Jun 21, 2023
@eleanorjboyd eleanorjboyd marked this pull request as ready for review June 21, 2023 16:23
@eleanorjboyd eleanorjboyd deleted the branch microsoft:resultResolver-feature-branch June 21, 2023 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-testing feature-request Request for new features or functionality skip tests Updates to tests unnecessary
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Dynamic run result in test explorer for pytest
2 participants