Skip to content

ANIKET KUMAR NISHAD — R50-T040: Strengthen the tests of CoPrimeCheck (CoPrimeCheck.js) [Maths/CoPrimeCheck.js] #40

Open

Description

@ankushbisht01

Student: ANIKET KUMAR NISHAD

Task: R50-T040 · 10 of 10
Repository: https://github.com/S-AI-Projects/TheAlgorithms-JavaScript
Assigned working branch: student/e26b07f0789

Goal

Work on Maths/CoPrimeCheck.js. Prove that a regression test can detect a plausible one-line mistake in CoPrimeCheck. Use the fixture and invariant: No emitted prime has a divisor from 2 through its integer square root; composite 9 must be rejected. Fixture: Use the supported domain around 1, 2, 9 and 11. For a sieve through 12 the primes are 2, 3, 5, 7 and 11; respect an exclusive upper-bound interface.

Steps

  1. Read Maths/CoPrimeCheck.js, especially CoPrimeCheck near line 21. Record its public inputs, result, mutation behavior and any external dependencies before changing it.
  2. In a temporary copy, alter one boundary comparison, accumulation or return condition relevant to the algorithm.
  3. Find a valid input for which the original and mutant differ; independently establish the correct output and reduce the input.
  4. Implement work/R50-T040/check.py as a focused runner that executes the new checks and propagates failures. Native check to incorporate: run the repository test script in non-watch mode after installing from its lockfile; for browser-only code use a browser test instead of plain Node. Record the actual command and nonzero test count.
  5. Create the checks specified below and run python3 work/R50-T040/check.py. Save inputs, expected versus actual results and tool versions in work/R50-T040/; a check must exit non-zero when an assertion fails.
  6. Commit the repository change on branch R50-T040; prepare a PR to the organisation fork explaining the result and linking the checks. Keep each task independently reviewable. Remove work/R50-T040/ from a later upstream branch.

Done when

☐ The checked behavior is tied to CoPrimeCheck in Maths/CoPrimeCheck.js; every assertion has an explicit expected value.
☐ Use the supported domain around 1, 2, 9 and 11. For a sieve through 12 the primes are 2, 3, 5, 7 and 11; respect an exclusive upper-bound interface.
☐ Existing supported behavior and the public interface are preserved unless a failing regression demonstrates and documents a defect.
☐ The original passes and the mutant fails the same named assertion for a semantic reason.
☐ The final implementation contains no mutation or test-only branch.

Additional task guidance

Additional curated task guidance

Item:
Maths/CoPrimeCheck.js

Task type:
Mutation-resistant tests

Code change (goes into the PR):
Add a focused regression in the normal tests for Maths/CoPrimeCheck.js and document the protected condition. Keep the deliberate mutant out of the final source.

Automated check:
python3 work/R50-T040/check.py

Prerequisites:
Node matching the project engines/CI, package manager selected by its lockfile, and Python 3.

Upstream PR rules:
Preserve the repository JavaScript style, use its test framework, and include JSDoc for changed public behavior. Submit coursework to the organisation fork first; keep work/ evidence out of any later upstream PR. Upstream acceptance is not a grading requirement. Policy: https://github.com/TheAlgorithms/JavaScript/blob/5c39e87a9a31f279c60f830ad74a845e4788a517/CONTRIBUTING.md

Source (pinned):
https://github.com/TheAlgorithms/JavaScript/blob/5c39e87a9a31f279c60f830ad74a845e4788a517/Maths/CoPrimeCheck.js#L21

Change:
Replaces the shared task template with an item-specific contribution brief.

PR destination:
Upstream candidate after review

Submission checklist

  • Complete this task and its checks.
  • Add the required evidence and link your pull request here.
  • Select this S-AI-Projects fork as the PR base repository.
  • Request instructor review.

Keep this PR focused on this task. Do not submit assignment PRs to the upstream repository.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions