Add more links to MSTest api docs

[Evangelink]

Summary

Describe your changes here.

Fixes #Issue_Number (if available)

---

Internal previews

📄 File	🔗 Preview link
docs/core/testing/unit-testing-mstest-writing-tests-assertions.md	MSTest assertions
docs/core/testing/unit-testing-mstest-writing-tests-attributes.md	MSTest attributes
docs/core/testing/unit-testing-mstest-writing-tests-testcontext.md	The TestContext class

[BillWagner]

Adding @gewarren

Do you know why the xrefs are generating warnings here?

[gewarren]

BTW, we have an extension for VS Code that inserts xrefs links. Do you know about it? It's a very helpful tool. https://github.com/IEvangelist/xref-helper/blob/main/README.md

[Evangelink]

BTW, we have an extension for VS Code that inserts xrefs links. Do you know about it? It's a very helpful tool. IEvangelist/xref-helper@main/README.md

I wasn't aware of it!

[Youssef1313]

Suggested change

	You can also use <xref:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.Write> or <xref:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.WriteLine> methods to write custom messages directly to the test output. This is especially useful for debugging purposes, as it provides real-time logging information within your test execution context.
	You can also use <xref:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.Write*> or <xref:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.WriteLine*> methods to write custom messages directly to the test output. This is especially useful for debugging purposes, as it provides real-time logging information within your test execution context.

[gewarren]

I left some comments - but these are only suggestions that you can decide for yourself about.

[gewarren]

I actually prefer the original display here. It still uses an xref and the word "attribute" isn't repeated. (When you use an xref like that (with custom text), you don't actually need the angle brackets.)

[gewarren]

Suggested change

	The method should have zero parameters, unless it's used with <xref:Microsoft.VisualStudio.TestTools.UnitTesting.DataRowAttribute>, <xref:Microsoft.VisualStudio.TestTools.UnitTesting.DynamicDataAttribute> or similar attribute that provides test case data to the test method.
	The method should have zero parameters, unless it's marked with <xref:Microsoft.VisualStudio.TestTools.UnitTesting.DataRowAttribute>, <xref:Microsoft.VisualStudio.TestTools.UnitTesting.DynamicDataAttribute>, or a similar attribute that provides test case data to the test method.

[gewarren]

Suggested change

	It's possible to control the inheritance behavior: only for current class using [InheritanceBehavior.None](<xref:Microsoft.VisualStudio.TestTools.UnitTesting.InheritanceBehavior>) or for all derived classes using [InheritanceBehavior.BeforeEachDerivedClass](<xref:Microsoft.VisualStudio.TestTools.UnitTesting.InheritanceBehavior>).
	It's possible to control the inheritance behavior: only for current class using <xref:Microsoft.VisualStudio.TestTools.UnitTesting.InheritanceBehavior.None?displayProperty=nameWithType>, or for all derived classes using <xref:Microsoft.VisualStudio.TestTools.UnitTesting.InheritanceBehavior.BeforeEachDerivedClass?displayProperty=nameWithType>.

[gewarren]

Suggested change

	- <xref:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.TestData> - the data that will be provided to the parameterized test method or `null` if the test is not parameterized.
	- <xref:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.TestData?displayProperty=nameWithType> - the data that will be provided to the parameterized test method, or `null` if the test is not parameterized.

[gewarren]

Suggested change

	- <xref:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.TestDisplayName> - the display name of the test method.
	- <xref:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.TestDisplayName?displayProperty=nameWithType> - the display name of the test method.

[gewarren]

Suggested change

	- <xref:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.TestException> - the exception thrown by either the test method or test initialize, or `null` if the test method did not throw an exception.
	- <xref:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.TestException?displayProperty=nameWithType> - the exception thrown by either the test method or test initialize, or `null` if the test method did not throw an exception.

[gewarren]

Suggested change

You can also use <xref:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.Write*> or <xref:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.WriteLine*> methods to write custom messages directly to the test output. This is especially useful for debugging purposes, as it provides real-time logging information within your test execution context.

You can also use <xref:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.Write*?displayProperty=nameWithType> or <xref:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.WriteLine*?displayProperty=nameWithType> methods to write custom messages directly to the test output. This is especially useful for debugging purposes, as it provides real-time logging information within your test execution context.