working dir option for blt_add_test
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 296
- Forks
- 66
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 1
Description
trying to debug some unit test issues and I was having a hard time finding output files
we should consider adding a WORKING_DIRECTORY arg to our blt_add_test()
I used the following directly:
```
add_test( NAME $
{arg_NAME}
COMMAND $
{test_command}
WORKING_DIRECTORY $
{runtime_output_directory}
)
```
and the output files showed up where I expected after make test (tests/)
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() implementation and reviewing how it assembles add_test(). Use the provided WORKING_DIRECTORY value, then run make test and verify that test output files appear under tests/ as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100