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

NuGet description incorrect for project loader #54

Closed
ketchup201 opened this issue Jan 11, 2023 · 4 comments · Fixed by #58
Closed

NuGet description incorrect for project loader #54

ketchup201 opened this issue Jan 11, 2023 · 4 comments · Fixed by #58
Assignees
Milestone

Comments

@ketchup201
Copy link

I know this is petty, but the NuGet description that appears for NUnit.Extension.NUnitProjectLoader v3.7.1 is incorrect.

Expected: NUnit engine extension that allows running NUnit projects which have a file extension of .nunit.
Actual Result: NUnit Engine extension for writing test result files in NUnit V2 format.

@OsirisTerje
Copy link
Member

I'll move this to the correct repository.
Feel free to raise a PR for this :-)

@OsirisTerje OsirisTerje transferred this issue from nunit/nunit3-vs-adapter Jan 11, 2023
@OsirisTerje
Copy link
Member

Feel free to raise a PR

@CharliePoole
Copy link
Collaborator

This is definitely a bug. Probably caused by copy/pasting the descriptions from the V2 Result Writer extension.

Note that nothing can be changed directly on nuget.org without uploading a new version, so even when this is fixed it won't change on nuget.org until we publish a new release.

@CharliePoole
Copy link
Collaborator

Related to this, this GitHub Release Description has the wrong extension names listed in the text. That could be fixed immediately in the release itself but might be present in the script that generates releases as well.

@CharliePoole CharliePoole self-assigned this Jun 7, 2024
@CharliePoole CharliePoole added this to the 3.7.2 milestone Jun 7, 2024
@CharliePoole CharliePoole modified the milestones: 3.7.2, 3.8 Jun 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants