Skip to content

Test coverage gaps for critical code paths #10

@dbravender

Description

@dbravender

Priority: Low

Description

Several important code paths lack test coverage:

  • No test for deps with details=true — the most complex and risky code path in deps.go
  • No test for concurrent RunSCC calls — would validate the mutex correctness
  • No negative-path test for HandleStats with a non-existent directory
  • compare and checklist tests are thin — only empty-input and basic smoke tests, no validation of output content/structure beyond non-emptiness

Suggested additions

  1. Test HandleDeps with details=true on a temp dir with a requirements.txt
  2. Test concurrent RunSCC calls with t.Parallel() or sync.WaitGroup
  3. Test HandleStats with a path that doesn't exist
  4. Test HandleChecklist output contains expected categories
  5. Test HandleCompare guidance contains key instructions

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions