Add environment variables to blt_add_test
Open
Nobody has claimed this yet.
feature
testing
- Dominant language
- C++
- Stars
- 296
- Forks
- 66
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 1
Description
This would be useful in many cases. This:
```
blt_add_test(NAME mytest COMMAND mytest)
set_property(TEST spin_bvh APPEND PROPERTY ENVIRONMENT "CUDA_VISIBLE_DEVICES=1")
```
could be changed to this:
```
blt_add_test(NAME mytest COMMAND mytest ENV_VARS "CUDA_VISIBLE_DEVICES=1")
```
ENV_VARS would be nice if it was some type of list
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the blt_add_test entry point and how it currently forwards test properties to CTest. Define how the ENV_VARS argument should accept a list, then verify that each supplied variable reaches the test environment and that existing blt_add_test usage remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100