This is fine, although the slightly unfortunate thing about writing the test this way is that you can't see what the actual texture contents are if they're wrong. I.e. could we instead just write the loaded values directly into the UAV/RTV and check them on CPU?