hey! this is a static git repo viewer. commit diffs, file history, older commits and other revisions won't load without javascript.

you are still able to view source files on branch tips, but the experience is degraded.

yum-mirror/glslang

git clone https://git.yummers.dev/yum-mirror/glslang

John KessenichMerge branch 'master' into hlsl-frontend1c7e70762016-04-03

renderedcode

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.

1Glslang Tests based on the Google Test Framework
2================================================
3
4This directory contains [Google Test][gtest] based test fixture and test
5cases for glslang.
6
7Apart from typical unit tests, necessary utility methods are added into
8the [`GlslangTests`](TestFixture.h) fixture to provide the ability to do
9file-based integration tests. Various `*.FromFile.cpp` files lists names
10of files containing input shader code in the `Test/` directory. Utility
11methods will load the input shader source, compile them, and compare with
12the corresponding expected output in the `Test/baseResults/` directory.
13
14How to run the tests
15--------------------
16
17Please make sure you have a copy of [Google Test][gtest] checked out under
18the `External` directory before building. After building, just run the
19`ctest` command or the `gtests/glslangtests` binary in your build directory.
20
21The `gtests/glslangtests` binary also provides an `--update-mode` command
22line option, which, if supplied, will overwrite the golden files under
23the `Test/baseResults/` directory with real output from that invocation.
24This serves as an easy way to update golden files.
25
26[gtest]: https://github.com/google/googletest