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

Consider using MSTest.Sdk or MSTest metapackage, or at least use MSTest.Analyzers #1076

Open
Youssef1313 opened this issue Nov 27, 2024 · 4 comments
Open

Consider using MSTest.Sdk or MSTest metapackage, or at least use MSTest.Analyzers #1076

Youssef1313 opened this issue Nov 27, 2024 · 4 comments
Assignees
@codeofdusk
Labels
status: resolved This issue has been merged into main.

Comments

@Youssef1313
Copy link
Member

Currently, MSTest analyzers are not used in this repo. You can consider using them by adding a reference to MSTest.Analyzers (with PrivateAssets="all"). Or use MSTest metapackage which includes all the needed dependencies, and then you will no longer need to have multiple package references related to testing.

Or you can even go further and use MSTest.Sdk.
@microsoft-github-policy-service microsoft-github-policy-service bot added the status: new This issue is new and requires triage by DRI. label Nov 27, 2024
@codeofdusk codeofdusk added status: ready for triage This issue is ready to be triaged by the Accessibility Insights team. and removed status: new This issue is new and requires triage by DRI. labels Nov 27, 2024
@microsoft-github-policy-service Microsoft GitHub Policy Service
Copy link
Contributor

This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!

@codeofdusk codeofdusk self-assigned this Nov 27, 2024
@JGibson2019 JGibson2019 added status: needs investigation This issue requires investigation (PM, Design, or SWE) by the Accessibility Insights team. and removed status: ready for triage This issue is ready to be triaged by the Accessibility Insights team. labels Dec 2, 2024
@microsoft-github-policy-service Microsoft GitHub Policy Service
Copy link
Contributor

This issue requires additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, we will update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights!

@codeofdusk codeofdusk mentioned this issue Dec 24, 2024
Merged
1 task
codeofdusk pushed a commit that referenced this issue Dec 24, 2024
@v-sharmachir
chore: Use of MSTest metapackage instead of multiple package referenc…
92d8406 
…es related to testing. (#1082)

This commit replaces various testing-related package references with the
`MSTest` metapackage, obviating the need for multiple package references
for testing.

addresses #1076
@Youssef1313
Copy link
Member Author

Closing as fixed by #1082

@codeofdusk
Copy link
Contributor

We usually keep issues open until a fix is released.

@codeofdusk codeofdusk reopened this Dec 24, 2024
@codeofdusk codeofdusk added status: resolved This issue has been merged into main. and removed status: needs investigation This issue requires investigation (PM, Design, or SWE) by the Accessibility Insights team. labels Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@codeofdusk codeofdusk

Labels
status: resolved This issue has been merged into main.
Projects
Accessibility Insights
Status: Needs triage
Milestone
No milestone
Development

No branches or pull requests
3 participants
@codeofdusk @JGibson2019 @Youssef1313