darktable-org / darktable-org/rawspeed
pointer to guidelines or requirements for tests
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 456
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
The pull request that could potentially provide canon CR3 decoding (R5,R6, M50, 250D, 90D to name a few young cameras)
is help up by what appears to be failing test coverage. Could someone point out the requirements for the test, and the way they integrate into the tests in general so that we get this boat floating again.
I might be able to provide a helping hand and are certainly interested in the result, both for the camera types and the testing technology.
Thanks.
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
The issue names no files, tests, or entry points, and refers generally to a CR3-decoding pull request. Start by locating that pull request and reviewing the repository's existing camera-decoder tests and test requirements. Done means the required test coverage and integration process are documented clearly enough to unblock the CR3 work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100