The BinDiff core engine should have a test suite with reasonable coverage

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
reverse-engineering, testing-qa

Research direction

Start by reviewing the existing end-to-end golden tests and the BinExport-based test inputs, then identify the BinDiff core engine boundaries that need direct coverage. Done means a maintainable core-engine test suite provides reasonable code coverage without relying only on the existing golden test set.

Written by the indexing model from the issue text.

Description

enhancement

BinDiff traditionally was only tested end-to-end running it on sets of BinExport files. While there is a large body of golden tests with expected results, any functional change to the core invalidates the existing test set. This makes implementation of new matching features or fixing long-standing issues unnecessarily hard.

Implement a test suite the has reasonable code coverage for the BinDiff core engine.

Internal bug: b/147221242

Dominant language
Java
Stars
3.2k
Forks
240
No merged PRs in 30d

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 google/bindiff

All issues in google/bindiff

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.