[Test] Add Zero-Value Expense Test Case to Finance Discipline Test Suite

Open Beginner friendly
#82 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
Under an hour
Newbie friendliness
92/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
testing

Research direction

Open tests/finance-discipline.test.ts and review the existing positive and negative cent allocation cases. Add the zero-value assertion for formatCentsToCurrency(0), then run npm run test:file -- tests/finance-discipline.test.ts and confirm the suite passes offline.

Written by the indexing model from the issue text.

Description

accessibility area:core beginner friendly bug community contributions-welcome difficulty:beginner difficulty:easy enhancement good first issue hacktoberfest help wanted testing time:<15m up-for-grabs
  • Labels: good first issue, testing, difficulty:beginner, area:core
  • Target File: tests/finance-discipline.test.ts
  • Estimated Time: 10–15 minutes
  • Difficulty: Level 2 (Beginner)
Why This Matters

Financial arithmetic in PACT OS requires strict boundary handling. Verifying that zero-value cents format correctly ensures financial ledgers render cleanly without negative sign zero (-$0.00) bugs.

Current Behavior

tests/finance-discipline.test.ts tests positive and negative cent allocations, but does not explicitly assert zero-cents formatting.

Requested Change

Add a test case in tests/finance-discipline.test.ts asserting that formatCentsToCurrency(0) returns "$0.00" and handles zero allocations without error.

Acceptance Criteria
  • Zero-value assertion added to tests/finance-discipline.test.ts.
  • Test suite executes cleanly offline with npm run test:file -- tests/finance-discipline.test.ts.
Verification
npm run test:file -- tests/finance-discipline.test.ts
Contributor Notes

Single-file test addition.


🚀 How to Claim and Implement an Issue

  1. Choose an Issue: Browse our open issues and pick one matching your interest and available time.
  2. Comment on GitHub: Leave a comment on the corresponding GitHub issue: "I would like to work on this issue. Please assign it to me."
  3. Follow the Guide: Review our Beginner's Contribution Guide for step-by-step Git instructions.
  4. Verify Locally: Run the specific verification command listed on the issue before opening your PR.
  5. Submit PR: Open a pull request against main referencing this issue number!
Dominant language
TypeScript
Stars
5
Forks
7
Avg merge
58m
Merged PRs (30d)
42

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TheVicky1/Pact_OS

All issues in TheVicky1/Pact_OS

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.