m4b / m4b/goblin

tests: binary data and us

Open
#185 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted
Dominant language
Rust
Stars
1.5k
Forks
202
PR merge metrics
No merged PRs in 30d

Description

We need to have a story for binary data in goblin, as it’s becoming more and more urgent to have a full test suite we can run against for compliance and regression.

We don’t want to store binary data in git, since this adds to clone time and is generally frowned against.

There are a few binary files in goblin or what is effectively binary data with vecs with u8s, but these are grandfathered, and we don’t need to concern ourselves with them.

Im open to any and all suggestions about what best path forward is here :)

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reviewing goblin’s existing binary files and vectors of u8s, noting that those grandfathered cases are out of scope. Determine how a compliance and regression test suite can cover binary data without storing binary files in git, then document the proposed approach and its completion criteria.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.