Hi there, we are researching on different options to enable people to review experiments and their given variants in production. I stumbled upon the QA-mode of the SDKs. I don't get the description. So, how does this mode work? Could enforce certain experiments and variants?

If true, random assignment is disabled and only explicitly forced variations are used.

Are there other approaches to enable reviews (especially for server-side experiments)?

There are a few ways: • You can use our Chrome developer tool (if its using js/react sdk) • You can do force values with the SDK or via the flags (like mark your users as QA and target them, or use the force variation methods • For web tests, you can also use query strings to force a variation

thx

@fresh-football-47124 - QQ it looks like the dev tools only work on Localhost. is there a way for my team who doesnt have our site running on their local to use the same dev tool?

you can enable it on any site

Hmmm… @fresh-football-47124 works well on our locahost, but not on our staging site for the rest of the non dev team. Any ideas?

@fresh-football-47124 before I am opening an issue on GitHub: If I add a

force rule

to my feature configuration (with an experiment rule) then it's appended instead of prepended. This behavior leads to a non-working

force rule

. Does this happen by intention? CC @adventurous-dream-15065 @numerous-army-92497

Hi Kobe - you can move the force rule up by dragging the 4 pointed arrow thing

Yes, I know. But (as a user) I would expect that force rules are prepended.