Re: [PATCH v3 0/4] MR418: Draft: tests/shader-runner: finer control over model ranges and [shader] directive execution for backends, part 1.

[Francisco Casas (＠fcasas)]

In person we have agreed upon going for gio's idea for the [require] directives, specifically the one where every shader model is manually specified.

We will make the default be:
```
[require]
shader model 2.0
shader model 4.0
shader model 6.0
```

I will work on this update for the MR so I will mark the current version as a Draft.

Regarding only having one [require] directive at the beginning of the file (when we want the tests to run on shader models other than the default ones), I don't think we should make it mandatory, just encourage it.