even if it is made from tutorials online a replicable test suite that helps
with the development of the 3D MESA library is needed.
interestingly this same test suite can be run against Kazan (or utilised
for testing of other 3D MESA Vulkan drivers)
The Vulkan conformance test suite should be the canonical location for all tests that are using the Vulkan API and not calling driver internals.
(In reply to Jacob Lifshay from comment #1)
> The Vulkan conformance test suite should be the canonical location for all
> tests that are using the Vulkan API and not calling driver internals.
> See https://salsa.debian.org/Kazan-team/kazan/-/blob/master/run-cts.sh
the idea here is not so much to prioritise or select one and only one "official" test suite, it is to collate *all* the test applications and suites (as submodules) that are used.
including that one you suggested about 8 or 9 days ago (what was it again?)
imagine vivek for example losing all work, the only thing he has online is the mesa branch being developed. everything else has to be recreated.
imagine soneone else joining and helping, they have to laboriously and manually install the same test programs.