I can't immediately think of what a useful shader test would look like (beyond perhaps, shader doesn't crash program) - if this is something worth discussing, i

I can't immediately think of what a useful shader test would look like (beyond perhaps, shader doesn't crash program) - if this is something worth discussing, it would probably be useful to see some real world shader code; perhaps especially two versions of the same shader as it evolve. I don't generally test css code to check that a background is now indeed set to "a more mauvey shade of pinky-russet" after a change - but I might want to. I might at least want to run a test with browser automation to check that any text is readable on the background. I could at least find an example of looking at the rendered page for text (as opposed to in the DOM); Google AI had some ideas of how to check the contrast in a screenshot - but no idea if that would actually work as written. https://medium.com/@dzianisv/vibe-engineering-testing-browser-automation-with-ocr-beyond-text-output-validation-717cef1d00d4 https://medium.com/@dzianisv/vibe-engineering-testing-browse... https://share.google/aimode/mW8ClhqGppfpovRrE https://share.google/aimode/mW8ClhqGppfpovRrE