-
Notifications
You must be signed in to change notification settings - Fork 853
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Google Test as the testing framework #189
Comments
Add I'll take on this. |
I agree things could be improved. At the moment it's quite cumbersome to fix the failing tests after a code change. There's no easy way to find which test failed first, no way to re-run it. I usually use some ad-hoc shell script to do just this. Are you proposing to replace diff tests with some new C++ unit tests, or just use Google Test as a test runner? |
@yavn: No, not only as a "test runner". The ideal outcome would be to rewrite all existing tests using the gtest framework, and I'll work towards that. On the other side, introducing gtest will make sure all future tests are written in a much clearer way. |
Done via #190. |
…mic_float_min_max Add header changes for SPV_EXT_shader_atomic_float_min_max
The existing test harness is a home-made shell script. All the tests and the expected results are written as plain text files in an integrated test style. This is not quite easy to maintain and slow to run.
The text was updated successfully, but these errors were encountered: