OpenAssetIO / OpenAssetIO/OpenAssetIO-TraitGen
De-couple test runtime environment from generation environment
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Following on from this fun, @feltech noted that:
[plan] This conflict only occurs due to tests, so it's a real shame it limits us in our production code.
I think the correct thing to do is isolate the CMake tests somehow. It is already a bit odd the way we build and run a CMake project from within a pytest test case. But that's obviously not a small fix.
Originally posted by @feltech in https://github.com/OpenAssetIO/OpenAssetIO-TraitGen/pull/31#discussion_r1267018457
It'd be great if we could decouple the test runtime from the generation runtime, so we don't have this conflict in the first place, as it's not a traitgen conflict per-se.
Contributor guide
No contributing guide indexed for this repository
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 with the pytest test case that builds and runs the CMake project, then trace how the generation and test runtime environments are configured. Done means the CMake tests no longer constrain the production generation environment and the existing test suite still passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, python
- Domain
- build-system, testing, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100