Docs: 3rd party libs

Author: egil

docs/site/docs/getting-started/fixture-details.md

@@ -109,4 +109,4 @@ Let's look at what's going on in this test:
 
 We will cover the details of the "act" and "assertion" step in the <xref:interaction> and <xref:verification> pages. 
 
-Learn more about injecting services into components under test on the <xref:inject-services-into-components> page.
+Learn more about injecting services into components under test on the <xref:inject-services> page.

docs/site/docs/getting-started/writing-csharp-tests.md

@@ -87,7 +87,7 @@ Then methods like <xref:Bunit.TestContext.RenderComponent``1(Bunit.Rendering.Com
 With the basics out of the way, we will next look at how to pass parameters and inject services into our components under test, and after that, cover in more details the various ways we can verify the outcome of a rendering.
 
 - <xref:passing-parameters-to-components>
-- <xref:inject-services-into-components>
+- <xref:inject-services>
 - <xref:verify-markup>
 - <xref:verify-component-state>
 - <xref:trigger-event-handlers>

docs/site/docs/getting-started/writing-razor-tests.md

@@ -90,15 +90,15 @@ In this example, we are passing both attribute parameters and child content to t
 
 [!code-html[](../../../samples/tests/razor/PassingParametersToComponents.razor)]
 
-Injecting services into the components under test is covered on the <xref:inject-services-into-components> page.
+Injecting services into the components under test is covered on the <xref:inject-services> page.
 
 ## Further Reading
 
 Now that we have covered the basics of writing tests using Razor syntax, you can continue digging deeper, e.g. by looking at:
 
 - <xref:fixture-details>
 - <xref:snapshottest-details>
-- <xref:inject-services-into-components>
+- <xref:inject-services>
 - <xref:verify-markup>
 - <xref:verify-component-state>
 - <xref:trigger-event-handlers>

docs/site/docs/providing-input/configure-3rd-party-libs.md

@@ -5,10 +5,13 @@ title: Configure 3rd Party Libraries for Testing
 
 # Configure 3rd Party Libraries for Testing
 
-General introduction about what is usually required: Mimic setup guide from lib in test.
+Testing a component that is built using a 3rd party component library can require additional setup steps in each test, to ensure the 3rd party components work correctly in a test context.
 
-Talk about following section containing specific instructions for 3rd parter libraries.
+If for example a 3rd party component requires services to be registered in production code, it is likely that this is needed in a test context as well. See the <xref:inject-services> page for more info on this.
 
-Add how to for test setup of tests that use Telerik, SyncFusion, etc. libraries. They often have IJsRuntime or other services that needs mocking or setup, before a test can run.
+Similarly, if a root component is needed to provide cascading values to the 3rd party components, that is likely to be needed as well. See the <xref:passing-parameters-to-components#cascading-parameters-and-cascading-values> page for more on this.
 
-The how to should be as minimal as possible, preferably with links to vendors own documentation, so we do not have to keep it up to date if the vendor changes something in their library.
+> [!TIP]
+> If you are a Blazor component vendor and have instructions on how to setup a bUnit test context for testing components that use your components, we would love to feature a link to your documentation and component library on this page. 
+> 
+> Just submit a pull-request to this page with the relevant links added, share the relevant links in [bUnit's gitter chat](https://gitter.im/egil/bunit), or add an issue on [bUnit's github page](https://github.com/egil/razor-components-testing-library/issues) with the relevant links.

docs/site/docs/providing-input/index.md

@@ -8,5 +8,5 @@ title: Providing Input to a Component Under Test
 This section covers the various ways to provide input to a component under test, its split into three sub sections:
 
 - **<xref:passing-parameters-to-components>:** This covers passing regular parameters, child content, cascading values, event callbacks, etc. This topic is mostly relevant when writing tests in C# only.
-- **<xref:inject-services-into-components>:** This covers injecting services into components under test. This topic is relevant for both Razor-based tests and C# only tests.
+- **<xref:inject-services>:** This covers injecting services into components under test. This topic is relevant for both Razor-based tests and C# only tests.
 - **<xref:configure-3rd-party-libs>:** This covers setting up 3rd party libraries in a bUnit testing scenario, such that components under test that use them can be tested easily.

docs/site/docs/providing-input/inject-services-into-components.md

@@ -1,5 +1,5 @@
 ---
-uid: inject-services-into-components
+uid: inject-services
 title: Injecting Services into Components Under Test
 ---
 

docs/site/docs/providing-input/passing-parameters-to-components.md

@@ -452,4 +452,4 @@ The special thing in this case is that the `GetComponentUnderTest<HelloWorld>()`
 
 ## Further Reading
 
-- <xref:inject-services-into-components>
+- <xref:inject-services>

docs/site/docs/toc.md

@@ -7,7 +7,7 @@
 
 # [Providing Input](xref:providing-input)
 ## [Parameters and Cascading Values](xref:passing-parameters-to-components)
-## [Inject Services into Components](xref:inject-services-into-components)
+## [Inject Services into Components](xref:inject-services)
 ## [Configure 3rd Party Libraries](xref:configure-3rd-party-libs)
 
 # [Interaction](xref:interaction)