indiana91/devstandup

Add Unit Tests for Git Analyzer

Open

#4 opened on Oct 2, 2025

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees) (0 forks)auto 404
good first issue

Repository metrics

Stars
 (1 star)
PR merge metrics
 (PR metrics pending)

Description

Write unit tests for the internal/git/analyzer.go file to ensure commit analysis works correctly.

Tasks:

  • Create analyzer_test.go file
  • Write test for parsing commit messages
  • Write test for calculating statistics (additions, deletions)
  • Write test for filtering commits by date range
  • Write test for filtering commits by author
  • Achieve at least 80% code coverage

Acceptance Criteria:

  • All tests pass with go test ./internal/git/...
  • Code coverage is at least 80%
  • Tests include edge cases (empty repos, no commits, etc.)

Resources:

Contributor guide

Research direction
Create the test file `internal/git/analyzer test.go` following Go test conventions. Write table driven tests for each function in `analyzer.go` covering normal cases, edge cases (empty repo, no commits), and verify statistics.
Tech stack
go
Domain
backendcli
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75