glslang/gtests
2016-07-08 22:09:10 -06:00
..
AST.FromFile.cpp SPV: Turn on atomic-storage functionality for SPIR-V. 2016-07-07 17:40:35 -06:00
BuiltInResource.FromFile.cpp Rename DefaultResourceLimits.* to ResourceLimits.*. 2016-05-19 13:53:16 -04:00
CMakeLists.txt For MinGW, statically link exes against basic runtimes 2016-06-02 14:37:24 -04:00
Config.FromFile.cpp Test compiling shaders with given resource limits using GTest. 2016-05-19 14:18:21 -04:00
Hlsl.FromFile.cpp HLSL: Add typedef grammar and production. 2016-07-05 00:02:40 -06:00
Initializer.h Add support for testing file-based HLSL source code in GTest. 2016-05-16 12:51:13 -04:00
Link.FromFile.cpp Check for linking multiple ES shaders to the same stage 2016-05-25 09:26:43 +02:00
main.cpp Link in Google Test framework. 2016-03-31 10:31:30 -04:00
Pp.FromFile.cpp Remove duplicated tests from the runtests script. 2016-06-28 17:54:07 -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 SPV: Fix issue #376; declare Geometry capability for fragment use of gl_Layer. 2016-07-08 14:05:15 -06:00
TestFixture.cpp Build: Remove causes of pedantic warnings. Addresses issue #352 and PR #242. 2016-07-08 22:09:10 -06:00
TestFixture.h Build: Remove causes of pedantic warnings. Addresses issue #352 and PR #242. 2016-07-08 22:09:10 -06: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.