Skip to content

[Test] Add Single-Item Boundary Test Case to Task Prioritization Test Suite #87

Description

@TheVicky1
  • Labels: good first issue, testing, difficulty:beginner, area:core
  • Target File: tests/tasks-validation.test.ts
  • Estimated Time: 10–15 minutes
  • Difficulty: Level 2 (Beginner)

Why This Matters

Sorting and ordering algorithms must gracefully handle single-element arrays without mutation errors or indexing issues.

Current Behavior

tests/tasks-validation.test.ts covers multi-item sorting, but lacks a dedicated single-element array boundary test.

Requested Change

Add a test case in tests/tasks-validation.test.ts verifying that prioritizing an array with 1 task returns that single task without errors.

Acceptance Criteria

  • Single-item sorting test case added to tests/tasks-validation.test.ts.
  • Test suite executes cleanly: npm run test:file -- tests/tasks-validation.test.ts.

Verification

npm run test:file -- tests/tasks-validation.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!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    accessibilityAccessibility / a11y improvements (ARIA attributes, keyboard navigation, contrast)area:coreCore domain logic, shared arithmetic helpers, security, and utility servicesbeginner friendlyAccessible task suitable for developers new to open sourcebugConfirmed defect, malfunctioning behavior, or validation errorcommunityCommunity-driven enhancement, UX feedback, or resource sharingcontributions-welcomeCommunity contributions are explicitly encouraged for this issuedifficulty:beginnerBeginner-friendly task with single-file scope and clear acceptance criteriadifficulty:easyStraightforward task requiring basic familiarity with React/TypeScriptenhancementSmall improvement, refinement, or feature expansiongood first issueCurated, self-contained task suitable for first-time contributorshacktoberfestEligible high-quality task for open-source community eventshelp wantedMaintainer is actively welcoming community contributions on this issuetestingUnit tests, test matrix expansion, validation fixtures, and regression coveragetime:<15mQuick fix, typo correction, or minor tweak (< 15 minutes)up-for-grabsUnassigned issue that is available for any contributor

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions