Repository navigation
Description
Student: Anjali Dewangan
Task: R51-T042 · 2 of 10
Repository: https://github.com/S-AI-Projects/javascript-algorithms
Assigned working branch: student/e26b07f0661
Goal
Work on src/algorithms/graph/breadth-first-search/breadthFirstSearch.js. Identify the smallest supported domain around initCallbacks and make its boundary behavior explicit. Use edges A–B, A–C, B–D and an isolated E. From A, distances are 0 to A, 1 to B/C and 2 to D; E is unreachable. Fixture: Use edges A–B, A–C, B–D and an isolated E. From A, distances are 0 to A, 1 to B/C and 2 to D; E is unreachable.
Steps
- Read src/algorithms/graph/breadth-first-search/breadthFirstSearch.js, especially
initCallbacksnear line 19. Record its public inputs, result, mutation behavior and any external dependencies before changing it. - Partition inputs into valid interior, valid boundary and explicitly unsupported values. Do not add rejection rules for behavior the source leaves undefined.
- Place one test on each side of a documented boundary, including the exact exception or sentinel only when specified.
- Implement work/R51-T042/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.
- Create the checks specified below and run
python3 work/R51-T042/check.py. Save inputs, expected versus actual results and tool versions in work/R51-T042/; a check must exit non-zero when an assertion fails. - Commit the repository change on branch R51-T042; prepare a PR to the organisation fork explaining the result and linking the checks. Keep each task independently reviewable. Remove work/R51-T042/ from a later upstream branch.
Done when
☐ The checked behavior is tied to initCallbacks in src/algorithms/graph/breadth-first-search/breadthFirstSearch.js; every assertion has an explicit expected value.
☐ Use edges A–B, A–C, B–D and an isolated E. From A, distances are 0 to A, 1 to B/C and 2 to D; E is unreachable.
☐ Existing supported behavior and the public interface are preserved unless a failing regression demonstrates and documents a defect.
☐ The boundary table cites the source contract, and every supported boundary is asserted.
☐ No arbitrary TypeError/RangeError policy is imposed across unrelated functions.
Additional task guidance
Additional curated task guidance
Item:
src/algorithms/graph/breadth-first-search
Task type:
Boundary cases
Code change (goes into the PR):
src/algorithms/graph/breadth-first-search/breadthFirstSearch.js: document the supported boundary and add focused boundary tests; change guards only where the documented contract requires them.
Automated check:
python3 work/R51-T042/check.py
Prerequisites:
Node matching project CI, the project lockfile dependencies, and Python 3.
Upstream PR rules:
Keep the contribution scoped to the named item and follow the linked contribution instructions and repository CI. 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/trekhleb/javascript-algorithms/blob/85293e3e2b88f4d2ce330d956b139cf628aa1e82/CONTRIBUTING.md
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