Ideal solution would be to have it first calculated based on executing assembly or similar; if it fails then read from an environment variable and if that also fails - used a hardcoded value.
All paths are stored inside a single file UnitTests.Defaults.cs, what is perfectly fine.
They are not spread around all the tests and current solution is flexible enough for multiple testers.
Ideal solution would be to have it first calculated based on executing assembly or similar; if it fails then read from an environment variable and if that also fails - used a hardcoded value.
Branch:
feature_ph_refactoring