TEST: review tests and add inlined secret size argument to test all generated key sizes
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6
- Forks
- 6
- Avg merge
- 8d 10h
- Merged PRs (30d)
- 4
Description
For example, see CaskSecrets_IsCask_InvalidKey_InvalidProviderKind which applies all key sizes to theory variants.
And CaskSecrets_GenerateKey_ValidTimestamps which applies all secret sizes as inlined data to a test theory.
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 by locating the CaskSecrets_IsCask_InvalidKey_InvalidProviderKind and CaskSecrets_GenerateKey_ValidTimestamps tests. Compare their theory data with the other key-generation tests, then run the relevant test project. Done means the tests include an inlined secret-size argument and cover all generated key sizes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100