deb-sig/double-entry-generator

Start to add more unit tests

Open

#144 opened on Feb 19, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (697 stars) (100 forks)user submission
enhancementgood first issuehelp wanted

Description

Is your feature request related to a problem? Please describe.

截至目前为止，本项目都还没有任何的单元测试, 我们有的只是基本账单文件的 end-to-end test, 软件开发的best practice 是 unit test >> integration test >> end-to-end test, 不过我们的现在是只有 end-to-end test.

Describe the solution you'd like 从现在开始，给项目增加单元测试用例

Describe alternatives you've considered 继续使用已有的end-to-end test, 但是随着项目支持 provider 的增多, 以及需要覆盖的场景的增加, 只有 end-to-end test 会显得力不从心.

Additional context #142

Contributor guide

Tech stack
go
Domain
testing
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingUnit testing experienceUnderstanding of project structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Start by examining the existing end to end tests and the project codebase to identify key units to test. Look at the project structure, especially the main packages (e.g., provider parsers, ledger generation). Review issue #142 for additional context. Write unit tests for core logic functions, following Go testing best practices. Consider using the standard testing package or testify if already present.