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.

Sign up for GitHub

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

Jump to bottom

fix test-results so that it is easier to locate tests #33328

Open
jeremymeng opened this issue Mar 10, 2025 · 0 comments
Open

fix test-results so that it is easier to locate tests #33328

jeremymeng opened this issue Mar 10, 2025 · 0 comments
Assignees
@jeremymeng
Labels
Client This issue points to a problem in the data-plane of the library. EngSys This issue is impacting the engineering system.

Comments

@jeremymeng
Copy link
Member

jeremymeng commented Mar 10, 2025 •
edited
Loading

Currently we've seen some less ideal experience in the test results. It deson't include the full file path so after test results are uploaded and merged what we see in Azure DevOps Tests page is just a relative path to the test files for the suite names. This makes it harder to locate the failing tests especially when there are results from multiple packages which have similar test case titles.

Image

We could probably fix the results by adding the package paths if there isn't an option to configure vitest
@jeremymeng jeremymeng added Client This issue points to a problem in the data-plane of the library. EngSys This issue is impacting the engineering system. labels Mar 10, 2025
@jeremymeng jeremymeng self-assigned this Mar 10, 2025
@jeremymeng jeremymeng changed the title fix test-results to include package path fix test-results so that it is easier to locate tests Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jeremymeng jeremymeng

Labels
Client This issue points to a problem in the data-plane of the library. EngSys This issue is impacting the engineering system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeremymeng