Experiment with including fuzz + mutation tests in the template

Open
#1,748 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
cli, testing-qa

Research direction

Locate the project template and inspect how its existing test setup is documented. Experiment with the cargo fuzz init and cargo mutant workflows, then decide whether the template should include full boilerplate, README guidance, or neither. Done means the chosen approach is documented or implemented with the trade-off recorded.

Written by the indexing model from the issue text.

Description

Experiment with including fuzz + mutation tests in the template.

There's a balance between making a template that's too overwhelming that turns folks away, so I'm not sure we want to do this. There's a couple options here:

  • Try this out, and decide not to change the template.
  • Try this out, and decide to include full boilerplate for fuzz and mutation tests.
  • Try this out, and decide to just include a README comment that says "run cargo fuzz init to setup fuzz tests", and that says to "run cargo mutant to run mutation tests".
Dominant language
Rust
Stars
123
Forks
141
Avg merge
2d 21h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stellar/stellar-cli

All issues in stellar/stellar-cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.