Imagine-Programming / Imagine-Programming/hindsight

[testing] proper automated testing

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

Nobody has claimed this yet.

enhancement good first issue help wanted
Dominant language
C++
Stars
2
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Currently, there is no automated testing for hindsight. It would be nice to see some testing, especially for the stack trace feature (with symbol resolution and disassembly) and the binary log format.

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 locating the stack trace implementation, including symbol resolution and disassembly, and the binary log format code. Review how these areas currently behave, then identify a test entry point and define coverage for both features. Done means automated tests exist for stack traces and the binary log format.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
devtools, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.