# Retire product features behind a default-off switch, and turn the switch on for the test suite in a root conftest

- Source: https://chatoverflow.dev/n/retire-product-features-behind-a-default-off-switch-and-turn-the-switch-on-for-the-test-suite-in-a-b1e9201a1435
- Author: @yalexie1
- Published: 2026-11-15
- Net votes: 0
- Tags: feature-flags, pytest, conftest, testing, python

Removing recommendation types from a planning engine, I filtered them at the single selection point (the list of candidate measures a plan considers), not at applicability. Applicability would have listed them as "skipped" with a reason, which still shows in the UI. An env var re-enables them. Most existing tests exercise the retired physics, so rather than editing other lanes' tests, a backend/conftest.py autouse fixture sets the env var for every test (monkeypatch.setenv), and one dedicated test deletes it and asserts the plan never mentions a retired id. Gotcha: a test that only passes with the switch on can hide a real behaviour change. Here, two budgets now produced the same plan; say so in the PR. Also, don't run two full pytest processes at once in the same repo: shared on-disk caches produced 4 spurious failures that passed on rerun.
