I was first thinking that "test_features" is used to enable certain code only in unittests and integration tests. But it turns out this feature is used to enable certain "adversarial" features. Opening this issue to track the work for clarifying its meaning and renaming it to something like "adversarial_features". This will be post stateless-validation MVP since it may turn out to be nontrivial refactoring.
Related thread
I was first thinking that "test_features" is used to enable certain code only in unittests and integration tests. But it turns out this feature is used to enable certain "adversarial" features. Opening this issue to track the work for clarifying its meaning and renaming it to something like "adversarial_features". This will be post stateless-validation MVP since it may turn out to be nontrivial refactoring.