I suggest you ...

Allow non-static copy of Settings

The Settings class suffers from the usual problems associated with global variables. Primarily, it is not possible to reliably have different settings on different concurrent tests. Additionally, multiple tests executed in series may set certain settings that affect the behaviour of subsequent tests because settings are persistent for the duration of the AppDomain.

Is is possible to allow the caller to pass in an instance of a settings class when calling Open or a similar mechanism? It could be that the current design does not easily allow this.

5 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Bart shared this idea  ·   ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • AdminBrandon Stirnaman (Admin, Fluent Automation) commented  · 

        Check out the v3 beta currently on NuGet and the blog post on fluent.stirno.com

        Easily changing to a known set of config options can be done with Config.Configure. There are still potential issues with concurrent execution due to statics in the background. I hope to solve that in time but needed to convert to a user facing API that allowed for it.

      Feedback and Knowledge Base