Unit test TODOs/FIXMEs
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14
- Forks
- 9
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 33
Description
Address the TODOs in unit test source:
-
test_MockBPA_Codecs:
https://github.com/NASA-AMMOS/BSL/blob/046549ebdaedc8e7d1d6627f994145fb57a7b7af/test/test_MockBPA_Codecs.c#L131-L135 -
test_PublicInterfaceImpl:
https://github.com/NASA-AMMOS/BSL/blob/046549ebdaedc8e7d1d6627f994145fb57a7b7af/test/test_PublicInterfaceImpl.c#L137 -
test_SamplePolicyProvider:
https://github.com/NASA-AMMOS/BSL/blob/046549ebdaedc8e7d1d6627f994145fb57a7b7af/test/test_SamplePolicyProvider.c#L115 -
test_BackendPolicyProvider:
https://github.com/NASA-AMMOS/BSL/blob/046549ebdaedc8e7d1d6627f994145fb57a7b7af/test/test_BackendPolicyProvider.c#L168 -
test_BackendSecurityContext:
https://github.com/NASA-AMMOS/BSL/blob/046549ebdaedc8e7d1d6627f994145fb57a7b7af/test/test_BackendSecurityContext.c#L181
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 with the five linked test files: test_MockBPA_Codecs.c, test_PublicInterfaceImpl.c, test_SamplePolicyProvider.c, test_BackendPolicyProvider.c, and test_BackendSecurityContext.c. Inspect each TODO or FIXME and the surrounding test setup, then run the unit test suite. Done means the listed TODOs are addressed and all tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- security, testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100