OpenTabletDriver / OpenTabletDriver/Plugin-Repository
Add simple PR tests
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Shell
- Stars
- 8
- Forks
- 37
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 3
Description
Some ideas:
| JSON Key | Check |
|---|---|
Name |
^.{2,}$ (2 characters or more) |
Description |
same as Name |
Owner |
^[^\s]+$ |
SupportedDriverVersion |
Must be lower than newest release, and have all 4 version subvalues (e.g. 0.6.4.0, not 0.6.4) |
PluginVersion |
^\d+(\.\d+){1,2}$ or less strict |
*Url |
must be curl'able (or similar) |
CompressionFormat |
Whatever we support, zip only for now? Can skip this check |
LicenseIdentifier |
Ideally, something from a predermined list, but otherwise same check as Owner |
Already covered in tests:
SHA256DownloadUrl
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 reviewing the existing tests for SHA256 and DownloadUrl, then identify where pull-request metadata is validated. Add focused checks for the listed JSON keys and confirm that valid and invalid plugin metadata are handled as intended.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100