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

Display results per node in test explorer (and maybe in console) #10

Open
IgorFedchenko opened this issue Feb 5, 2020 · 2 comments
Open
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@IgorFedchenko
Copy link
Contributor

As described in this section of TestAdapter how-to it is possible to show several results per one spec. Example is how xunit shows results for [Theory] marked tests.

Might be a good idea to display each node's result in such way, and global spec result in parent node.

@IgorFedchenko
Copy link
Contributor Author

After merging of #18 each node's spec is reported as separate test result. So need to group that results into single TestCase to make them children on one node in test explorer (and maybe they will be grouped in dotnet test output as well).

@IgorFedchenko IgorFedchenko added the enhancement New feature or request label Feb 8, 2020
@IgorFedchenko IgorFedchenko added this to the 1.2.0 milestone Feb 13, 2020
@Aaronontheweb Aaronontheweb modified the milestones: 1.2.0, v1.1.0 Oct 29, 2021
@Aaronontheweb
Copy link
Member

I know our .trx formatter used to support this on the back-end:

image

Link to test run (retained)

Now when we have an MNTR failure inside Azure DevOps it looks like this instead:

image

Link to test run (retained)

We've lost the "tree" output that we used to have - in the past it was our customer TrxExporter that handled this. The VSTestAdapter output should handle it now, so we likely need to change how we're structuring results in order to solve both problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants