TheVicky1 / TheVicky1/Pact_OS

[Test] Add Boundary Test Case for Max Budget Percentage in Budget Remaining Test Suite

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

Nobody has claimed this yet.

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
Dominant language
TypeScript
Stars
5
Forks
7
Avg merge
39m
Merged PRs (30d)
39

Description

  • Labels: good first issue, testing, difficulty:beginner, area:core
  • Target File: tests/budget-remaining.test.ts
  • Estimated Time: 10–15 minutes
  • Difficulty: Level 2 (Beginner)
Why This Matters

Financial budget tracking in PACT OS must handle exact 100% budget consumption boundary conditions without rounding errors, negative zero artifacts, or unexpected status calculation exceptions.

Current Behavior

tests/budget-remaining.test.ts verifies basic budget allocations, but does not explicitly test the exact 100% spent boundary condition.

Requested Change

Add a unit test case in tests/budget-remaining.test.ts asserting that when total expense equals total budget, remainingCents equals 0 and percentageUsed equals 100 cleanly.

Acceptance Criteria
  • 100% budget utilization boundary test case added to tests/budget-remaining.test.ts.
  • Test suite executes cleanly offline: npm run test:file -- tests/budget-remaining.test.ts.
Verification
npm run test:file -- tests/budget-remaining.test.ts
Contributor Notes

Single test case 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!

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.

Research direction

Start with tests/budget-remaining.test.ts and review the existing budget allocation cases. Add a case where total expense equals total budget, then run npm run test:file -- tests/budget-remaining.test.ts and confirm remainingCents is 0 and percentageUsed is 100.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.