We had a discussion about this in person and these are the main takeaways I gathered: * We want `.shader_test` file to only have at most one `[require]` directive, and have it at the top of the file, so that we don't have all the problems connected with changing the requirements mid-file. Files that require testing under different requirements will have to be split. * This `[require]` directive should list all the shader models that make sense for whatever is tested, so that there is no need for guesswork (in the form of the current "pick the minimum supported SM" rule) by the runner. For the SMs not supported by the runner, there is nothing to test. This is considered a compromise between running at all possible shader models (expensive) and resorting to complicated logics to pick the shader models that make sense by intersecting what the shader test supports, what the shader runner supports and using some heuristic.
Does everybody feel represented by this? Did I miss anything? We can keep the conversation going.