CI: Test our *2john tools
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
We need to start automatic testing of our *2john tools, perhaps on GitHub Actions using inputs from our https://github.com/openwall/john-samples repo. Most of these tools are Python scripts and some have dependencies, so this task might not be completed in one step. It's OK to start with testing our C compiled programs, then proceed to add more.
Also, maybe some of this (not requiring large input files) should become part of our make check (and individual tests automatically skipped when dependencies are not satisfied? so that make check remains usable to test john itself everywhere it currently is).
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
Review the *2john tools, the openwall/john-samples repository, and the existing GitHub Actions and make check entry points. Begin by identifying a small set of C-compiled tools and their inputs, then define how dependency-sensitive tests should behave. Done means automated coverage exists for an initial set without making make check unusable when optional dependencies are absent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, github-actions, python
- Domain
- build-system, ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100