Google Git
Sign in
fuchsia / third_party / github.com / KhronosGroup / Vulkan-Utility-Libraries / 7acfe4afbe40666b4e1d8a736e9c1eb4a7b1c1c1 / . / tests
tree: 281532e75a49de11fec1e07906b2500148e13bf8 [path history] [tgz]
  1. integration/
  2. CMakeLists.txt
  3. README.md
  4. struct_helper.cpp
  5. test_formats.cpp
  6. test_interface.cpp
  7. test_setting_api.cpp
  8. test_setting_cast.cpp
  9. test_setting_cpp.cpp
  10. test_setting_env.cpp
  11. test_setting_file.cpp
  12. test_setting_util.cpp
  13. vk_enum_string_helper.cpp
tests/README.md

Library integration testing

In order to avoid disruption of downstream users. It's important to test how this repository is consumed.

  1. Self contained headers

It‘s easy to write header files that aren’t self contained. By compiling a single source file that includes a single header we ensure a smooth experience for downstream users.

  1. Ensure C compatibility of C header files

It's VERY easy to write invalid C code. Especially for experience C++ programmers.

tests/find_package

Test find_package support. The intent is to ensure we properly install files.

Used by system/language package managers and the Vulkan SDK packaging.

tests/add_subdirectory

  1. Test add_subdirectory support

While we don't have to support add_subdirectory it is a common feature request for CMake projects.

  1. Ensure file name consistency of header files we install

All header files we ship will have the vk_ prefix

This convention was originally established in VulkanHeaders for files created by LunarG.

  • EX: vk_icd.h, vk_layer.h, vk_platform.h