Access to a more advanced test runner

[mystic harness]

I've often had the local test runner say everything is fine, only to be surprised with a massive test report.
The test report uncovers things the log from the game does not mention, nor the test runner. So you're basically working in the blind when you try your best to fix the issues.

You can only guess, resubmit, and in a few days (or some times weeks) you will get a new report only to see the issue persists, or even worse, there is a new issue with the assets you tried to correct.

The test runner has become more advanced, and I'm happy to see that, but it does not show the full picture, and it is both frustrating and confusing.

[brisk hinge]

The public testrunner already contains the majority of shader conflicts, as it cannot simulate the actual hardware the check is not 100% identical as we have it on devkits.
The testrunner for public is constantly being improved. If you have a particular case we can look into caching the shader conflict.
Please use the bugreport tool for this case and make sure to select the testrunner project for this report.

!bugreport