QA a flag before you ramp (and share a repro link)
Use the devtools overlay (Shift+Alt+S / ?se=1) and ?se_gate_… URL overrides to QA a feature, demo a variant, and reproduce a bug — all session-scoped.
A flag is built but sitting at 0%, and QA needs to verify it before you ramp. You don't want to flip the dashboard (that's everyone) and you don't want a special build (that's a deploy). You want to see the feature on your own screen, right now — and ideally hand a teammate a link that reproduces the exact state.
The browser SDK ships a devtools overlay for precisely this: flip any gate, config, experiment, or translation for your session only.
Open the overlay
- Press
Shift+Alt+Son any page running the SDK, or - append
?se=1to the URL.
It mounts in a Shadow DOM overlay, lists every resource in your project's blob, and lets you toggle each one. Your changes apply to your session and nobody else's.
Overrides live in your browser for the session — they never write to the dashboard and never affect other users. Close the session and you're back to the real evaluation.
Share a repro link with URL overrides
For QA flows, demos, and bug reports, force state straight from the URL — paste the link and the receiver lands in the same state:
| Param | Effect |
|---|---|
?se_gate_<name>=true | Force a gate on/off |
?se_config_<key>=<value> | Force a config value |
?se_exp_<name>=<group> | Force an experiment group |
For example, https://app.example.com/checkout?se_gate_new_checkout=true shows the QA reviewer the new checkout while it's still at 0% for real traffic.
These sit between programmatic overrides and the server's evaluation in precedence:
programmatic override > URL / devtools override > the server's evaluationRollout & measurement plan
- QA at 0%, then ramp. Verify the feature on your own session before any real user is in the rollout — the URL override is your pre-flight check.
- Demos without a deploy. Flip an experiment variant live in front of a customer, then close the session.
- Bug repro links beat screenshots. A
?se_gate_…link reproduces the exact state for whoever opens it, so the bug is reproducible instead of described.
Migrate off another flag vendor via OpenFeature
Drop ShipeasyProvider in behind the OpenFeature API so your existing getBooleanValue(...) call sites keep working unchanged.
Run conflicting experiments on one surface without interference
Put two experiments that touch the same surface in the same universe so a user is assigned to at most one — and neither confounds the other.