...
The features and tests relate exclusively to the core protocol spec, any other normatively referenced specs, and software components that serve as protocol endpoints. None relate to the Binding Obligations specification because it describes expected behaviors of operators and users of these endpoints, which makes them untestable for the purposes of an interop.
The type values for a test are at a minimum either "req" (required) or "opt" (optional). A test may additionally be of type "rptbearer" (specific to the "bearer" RPT profile) and "claimoidc" (specific to the OpenID Connect claim profile). Tests could be added to cover additional UMA WG-specified or third-party profiles, in which case the possible type values will expand. Generic high-level features of the protocol have an ID in the form "F-", and they group feature tests that have an ID in the form "FT-".
F-as-config: AS makes available its configuration data in the correct form at the correct location
...