summaryrefslogtreecommitdiffstats
path: root/Tests/FindPackageTest
diff options
context:
space:
mode:
authorMatthew Woehlke <matthew.woehlke@kitware.com>2024-08-01 18:59:47 (GMT)
committerMatthew Woehlke <matthew.woehlke@kitware.com>2024-08-14 19:25:27 (GMT)
commit1a846c8849c47f5871afaed68468de26d49af29e (patch)
tree8e77bb7635e4189bf892c76958f031eb80dbc37e /Tests/FindPackageTest
parent3d52d70b84b114adf36a176c6f05aa0f42b1326f (diff)
downloadCMake-1a846c8849c47f5871afaed68468de26d49af29e.zip
CMake-1a846c8849c47f5871afaed68468de26d49af29e.tar.gz
CMake-1a846c8849c47f5871afaed68468de26d49af29e.tar.bz2
Tests: Add tests for install(PACKAGE_INFO)
Add several test cases to verify that install(PACKAGE_INFO) is working as expected. These cover validating the output for several scenarios, improper use of the command, effects of command arguments, and a handful of improper uses. Tests that should still be added include one covering DESTINATION (both the default and user-specified) and the CPS location and link_location attributes. These have been skipped for now because the former requires actually installing a test project, and the latter involves validating attributes whose values are platform-dependent. (In particular, I don't think link_location will appear on not-Windows.) Additionally, there is no coverage of (other) common install-command arguments such as PERMISSIONS, COMPONENT, etc.; however, because the logic implementing these is shared, the tests covering them for other sub-commands is probably sufficient. Note that, because the files are generated in a location that includes a hash of the install destination, and because the default destination is platform dependent, the tests need to specify a fixed DESTINATION so that the location of generated files (which we need to inspect and validate) is predictable.
Diffstat (limited to 'Tests/FindPackageTest')
0 files changed, 0 insertions, 0 deletions