Combine Configuration, Services and AssertionOptions

[dennisdoomen]

We currently have two different entry points for configuration. One, the Services.Configuration, is used for specifying where to find custom value formatters and which test framework to use, and can be configured through app.config (provided the .NET platform supports that). The other, AssertionOptions, is used to change formatting settings and alter the equivalency plan.

We need one class for this that combines all of these settings, and that all support using the configuration system of .NET. This supports setting them through .ini files, .json files and environment variables.

The proposal is to name this class AssertionEngine, with properties like Runtime to contain run-time settings for the engine and Options for the settings that can be changed by tests.

Relates to #2290

[lg2de]

It would be great if these settings are not static.
When executing tests in parallel they must not influence each other.

[dennisdoomen]

I can't think of a way to make that possible. You?

[jnyrup]

It would be great if these settings are not static.

When executing tests in parallel they must not influence each other.

I'm not sure what you're asking for?
Currently they are static exactly to be shared and used among tests (running in parallel), but must be configured from a thread-safe point, e.g. module initializer or in a test framework dedicated way.

[lg2de]

I can't think of a way to make that possible. You?

Not yet in detail. I need to investigate.

I'm not sure what you're asking for?

I remember that I faced issues, at least with the tests in FA itself: Running tests with different configuration may conflict.

This may happen in end-user's tests too. This depends on the kind of option. I do not have an overview at the moment.

What are you assumptions for test configuration in different test assemblies?