steve/go-extractor
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Epic: Test Coverage #4

New Issue
Closed
opened 2026-02-14 16:05:22 +00:00 by Claude · 2 comments
Claude commented 2026-02-14 16:05:22 +00:00
Collaborator
Copy Link

Parent epic for improving test coverage across the project.

Current state

The core library types (Node, Nodes, Cookie, CookieJar, Readability, DeferClose) have good unit test coverage with mock implementations. However, all site-specific extractors (duckduckgo, google, powerball, megamillions, wegmans, aislegopher, archive, useragents) have no meaningful tests because they require a live browser.

Scope

  • Add mock-based unit tests for site extractors where possible
  • Add integration test framework
  • Test error paths in browser initialization

Sub-tasks

Will be linked as they are created.

Parent epic for improving test coverage across the project. ## Current state The core library types (Node, Nodes, Cookie, CookieJar, Readability, DeferClose) have good unit test coverage with mock implementations. However, all site-specific extractors (duckduckgo, google, powerball, megamillions, wegmans, aislegopher, archive, useragents) have no meaningful tests because they require a live browser. ## Scope - Add mock-based unit tests for site extractors where possible - Add integration test framework - Test error paths in browser initialization ## Sub-tasks Will be linked as they are created.
Claude added the priority/mediumtestingtype/epic labels 2026-02-14 16:05:33 +00:00
Claude commented 2026-02-14 16:09:06 +00:00
Author
Collaborator
Copy Link

Sub-tasks

  • #21 - Add mock-based unit tests for site extractors (medium)
## Sub-tasks - #21 - Add mock-based unit tests for site extractors (medium)
Claude commented 2026-02-15 20:57:42 +00:00
Author
Collaborator
Copy Link

Resolved by PR #43 — added extractortest package with exported mock implementations and HTML fixture-based tests for multiple extractors.

Closing this epic.

Resolved by PR #43 — added `extractortest` package with exported mock implementations and HTML fixture-based tests for multiple extractors. Closing this epic.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working correctly
 claude
Trigger — Steve has marked this issue for Claude to work on.
 claude:blocked
Blocked — Waiting on a dependency (another issue/repo).
 claude:review
In Review — PR created, awaiting human review/merge.
 claude:running
Active — A Claude instance is currently working on this.
 documentation
Documentation improvements or additions
 enhancement
New feature or improvement to existing functionality
 performance
Performance optimization or resource usage improvement
 priority/critical
Showstopper — security vulnerability, data loss, or crash in production
 priority/high
Important — significant bug or high-value improvement
 priority/low
Nice to have — minor improvement or cleanup
 priority/medium
Normal — standard improvement or non-critical bug
 security
Security-related issue or vulnerability
 testing
Test coverage, test infrastructure, or test improvements
 type/epic
Parent issue grouping related stories/tasks
 type/refactor
Code restructuring without behavior change
 type/task
Concrete implementation work item
No Label priority/medium testing type/epic
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Claude fizi steve
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: steve/go-extractor#4
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?