glslang/gtests
John Kessenich e2d06dbf60 Merge pull request #268 from AWoloszyn/update-cmake
CMake: Updated to better organize folders and options.
2016-05-05 13:46:36 -06:00
..
AST.FromFile.cpp Link in Google Test framework. 2016-03-31 10:31:30 -04:00
BuiltInResource.FromFile.cpp Link in Google Test framework. 2016-03-31 10:31:30 -04:00
CMakeLists.txt Install the test executable alongside glslangValidator 2016-05-05 14:58:26 -04:00
Initializer.h Remove use of std::mutex in gtest code. 2016-04-21 15:56:33 -04:00
main.cpp Link in Google Test framework. 2016-03-31 10:31:30 -04:00
Pp.FromFile.cpp Link in Google Test framework. 2016-03-31 10:31:30 -04:00
README.md Link in Google Test framework. 2016-03-31 10:31:30 -04:00
Settings.cpp Link in Google Test framework. 2016-03-31 10:31:30 -04:00
Settings.h Link in Google Test framework. 2016-03-31 10:31:30 -04:00
Spv.FromFile.cpp Implement the extension GL_ARB_shader_ballot 2016-05-05 19:02:35 +08:00
TestFixture.cpp Link in Google Test framework. 2016-03-31 10:31:30 -04:00
TestFixture.h Create a new logger class for all messages w.r.t. SPIR-V build. 2016-05-05 10:15:06 -04:00

Glslang Tests based on the Google Test Framework

This directory contains Google Test based test fixture and test cases for glslang.

Apart from typical unit tests, necessary utility methods are added into the GlslangTests fixture to provide the ability to do file-based integration tests. Various *.FromFile.cpp files lists names of files containing input shader code in the Test/ directory. Utility methods will load the input shader source, compile them, and compare with the corresponding expected output in the Test/baseResults/ directory.

How to run the tests

Please make sure you have a copy of Google Test checked out under the External directory before building. After building, just run the ctest command or the gtests/glslangtests binary in your build directory.

The gtests/glslangtests binary also provides an --update-mode command line option, which, if supplied, will overwrite the golden files under the Test/baseResults/ directory with real output from that invocation. This serves as an easy way to update golden files.