Sapna Shankar Talke — R45-T002: Define the supported boundaries of LineIntersection (LineIntersection.java) [src/main/java/com/thealgorithms/geometry/LineIntersection.java] #2

Student: Sapna Shankar Talke

Task: R45-T002 · 2 of 10
Repository: https://github.com/S-AI-Projects/TheAlgorithms-Java
Assigned working branch: student/e26b07f0703

Goal

Work on src/main/java/com/thealgorithms/geometry/LineIntersection.java. Identify the smallest supported domain around LineIntersection and make its boundary behavior explicit. Use the smallest valid input and one ordinary input for LineIntersection from src/main/java/com/thealgorithms/geometry/LineIntersection.java. Write the literal inputs and independently calculated expected outputs in the tests before editing the implementation. The check must name the source line establishing each precondition. Fixture: Use the smallest valid input and one ordinary input for LineIntersection from src/main/java/com/thealgorithms/geometry/LineIntersection.java. Write the literal inputs and independently calculated expected outputs in the tests before editing the implementation. The check must name the source line establishing each precondition.

Steps

1. Read src/main/java/com/thealgorithms/geometry/LineIntersection.java, especially LineIntersection near line 10. Record its public inputs, result, mutation behavior and any external dependencies before changing it.
2. Partition inputs into valid interior, valid boundary and explicitly unsupported values. Do not add rejection rules for behavior the source leaves undefined.
3. Place one test on each side of a documented boundary, including the exact exception or sentinel only when specified.
4. Implement work/R45-T002/check.py as a focused runner that executes the new checks and propagates failures. Native check to incorporate: mvn test (JDK 21 as specified in pom.xml); use JUnit in the corresponding src/test/java package. Record the actual command and nonzero test count.
5. Create the checks specified below and run python3 work/R45-T002/check.py. Save inputs, expected versus actual results and tool versions in work/R45-T002/; a check must exit non-zero when an assertion fails.
6. Commit the repository change on branch R45-T002; prepare a PR to the organisation fork explaining the result and linking the checks. Keep each task independently reviewable. Remove work/R45-T002/ from a later upstream branch.

Done when

☐ The checked behavior is tied to LineIntersection in src/main/java/com/thealgorithms/geometry/LineIntersection.java; every assertion has an explicit expected value.
☐ Use the smallest valid input and one ordinary input for LineIntersection from src/main/java/com/thealgorithms/geometry/LineIntersection.java. Write the literal inputs and independently calculated expected outputs in the tests before editing the implementation. The check must name the source line establishing each precondition.
☐ 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.

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.