hackforla / hackforla/lucky-parking

[Epic]: Establish unit testing and initial test coverage

Open
#732 0 comments 0 reactions 0 assignees View on GitHub
agile: epic
Dominant language
Jupyter Notebook
Stars
37
Forks
60
Avg merge
13h 32m
Merged PRs (30d)
5

Description

### User Story

As a development team, we want a supported unit-testing approach and initial test suite, so that changes can be validated reliably and regressions caught early.

### Description

Select and configure a unit-test runner, potentially Vitest; establish conventions; and add high-value initial coverage.

Out of scope: end-to-end testing, browser automation, and Playwright.

### Success Metrics

- Runner selected and rationale documented.
- Tests run through the existing workflow and CI where applicable.
- Conventions and guidance documented.
- Initial high-value unit tests added.

### Additional Information

Child Tasks cover audit, runner selection, configuration, conventions, initial coverage, and workflow validation.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the child tasks for the audit, runner selection, configuration, conventions, initial coverage, and workflow validation; no files or tests are named in the issue. Done means a runner and rationale are documented, tests run through the existing workflow and applicable CI, conventions are documented, and high-value unit tests are added without introducing end-to-end or browser automation.

Written by the indexing model from the issue text.

Assessment

Domain
ci-cd, documentation, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.