Use TestContext as base class for Passing parameters to components

[linkdotnet]

For the whole section of "Passing parameters to components" I used the TestContext as a base class and not instantiating a new one on every test.

This is anyway the recommended way - I added that that in the beginning as well.

I also used file-scoped namespaces in the regular plain old c# tests.

Edit: We can make this the defacto standard for every documentation if you wish and showing only one example how to instantiate a new TestContext just to be complete.

[egil]

Awesome, think the number of issues and questions we are seeing makes this a good change.

[linkdotnet]

Should I also "refactor" the other tests in this PR or do we want to do this later?
PS: I can't merge the PR as I am not eligible to merge to stable

[egil]

Should I also "refactor" the other tests in this PR or do we want to do this later?

Let's get all examples converted. I also think we should consider expanded the included lines in each example such that they show we are inheriting.

[linkdotnet]

Should I also "refactor" the other tests in this PR or do we want to do this later?

Let's get all examples converted. I also think we should consider expanded the included lines in each example such that they show we are inheriting.

Understood - I will ping when I am done. Will do some smaller commits as I have to sync between my Mac and Windows and stuff.

[linkdotnet]

So I refactored all the code examples to use the TestContext by default - I also added a small passage on how to do "the old" or less convenient way (aka newing up an instance).

I would advise that you check out the branch locally and check with docfx - I do think I hit everything, but 4 eyes are better.

[egil]

Thanks Steven. I'll check tomorrow. Had a day of travels.

[egil]

I spotted a few things I wanted to change and have pushed a PR.

There are a few other places where I saw some inconsistencies with indention (in the code in docs its 2 spaces instead of a tab, as we use in the code).

On the "writing a test" page, should the NUnit and MSTest samples also be upgraded to use the inheriting trick?

[linkdotnet]

I spotted a few things I wanted to change and have pushed a PR.

There are a few other places where I saw some inconsistencies with indention (in the code in docs its 2 spaces instead of a tab, as we use in the code).

On the "writing a test" page, should the NUnit and MSTest samples also be upgraded to use the inheriting trick?

Darn. I'll have a look later. Yeah Rider probably formats on save and for some reasons ignores the .editorconfig completly.

[linkdotnet]

Oh I found out why: our .editorconfig has old or non-existing values: tab_size doesn't exist anymore. Will add it as commit and align that stuff

[linkdotnet]

Pushed the indentation stuff to 2 - also updated editorconfig files as well as some examples in nunit/msunit

[egil]

Changed the wording on getting started again, and updated index too. Please look through those pages and let me know what you think.

[linkdotnet]

Currently only limited to my mobile as I am on a short vacation so did. only had s short look, but looked good 👍
From my point of view it definitely is now a much rounder picture