Skip to content

London | 26-ITP-May | Dipa Sarker | Sprint 3 | Implement and rewrite final#1470

Open
Dipa-Sarker wants to merge 4 commits into
CodeYourFuture:mainfrom
Dipa-Sarker:Coursework/sprint-3-implement-and-rewrite-final
Open

London | 26-ITP-May | Dipa Sarker | Sprint 3 | Implement and rewrite final#1470
Dipa-Sarker wants to merge 4 commits into
CodeYourFuture:mainfrom
Dipa-Sarker:Coursework/sprint-3-implement-and-rewrite-final

Conversation

@Dipa-Sarker

Copy link
Copy Markdown

Learners, PR Template

Self checklist

  • I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title
  • My changes meet the requirements of the task
  • I have tested my changes
  • My changes follow the style guide

Changelist

  1. Implemented the required functionality for the angle type, proper fraction and card value logic.
  2. Rewrote and expanded the tests using Jest.
  3. Added test cases to verify expected behavior and improve test coverage.
  4. Refactored the implementation where needed to ensure the code passes all Jest tests.

@Dipa-Sarker

Copy link
Copy Markdown
Author

Hello Reviewers,
I just wanted to inform that, I made several mistakes creating branching for each of the sprints (Sprint-1, Sprint-2, Sprint-3/implement and re-write tests, Sprint-3/Practice-tdd. After so many attempts I was able to create separate branches and for that reason I named this branch "implement and re-write final". I hope I will more conscious about this issue in near future. Thank you.

@Dipa-Sarker Dipa-Sarker added the Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. label Jul 6, 2026
if (angle <= 0 || angle >= 360) {
return "Invalid angle";
}
else if (angle == 90) {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whats the difference between == and === and why are you using == here?

Comment on lines +83 to +97
//module.exports = getAngleType;

// This helper function is written to make our assertions easier to read.
// If the actual output matches the target output, the test will pass
// function assertEquals(actualOutput, targetOutput) {
//console.assert(
//actualOutput === targetOutput,
//`Expected ${actualOutput} to equal ${targetOutput}`
//);
//}

// TODO: Write tests to cover all cases, including boundary and invalid cases.
// Example: Identify Right Angles
//const right = getAngleType(90);
//assertEquals(right, "Right angle"); No newline at end of file

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is there commented out code?

Comment on lines +12 to +22
expect(getAngleType(91)).toEqual("Obtuse angle");
expect(getAngleType(120)).toEqual("Obtuse angle");
expect(getAngleType(179)).toEqual("Obtuse angle");
});
test(`should return "Straight angle" when (0 == 180)`, () => {
expect(getAngleType(180)).toEqual("Straight angle");
});
test(`should return "Reflex angle" when (180 < angle < 360)`, () => {
expect(getAngleType(181)).toEqual("Reflex angle");
expect(getAngleType(270)).toEqual("Reflex angle");
expect(getAngleType(359)).toEqual("Reflex angle");

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job on testing the border cases here

Comment on lines +25 to +26
expect(getAngleType(-1)).toEqual("Invalid angle");
expect(getAngleType(370)).toEqual("Invalid angle");

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which border cases can you test here? (Which numbers are closest to the condition?)

Comment on lines +23 to +28
test(`should return false when numerator is negative`, () => {
expect(isProperFraction(-1, 1)).toEqual(false);
});
test(`should return false when denominator is negative`, () => {
expect(isProperFraction(1, -1)).toEqual(false);
}); No newline at end of file

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about values like -1/2 or 1/-2. What should the function return for them?


function isProperFraction(numerator, denominator) {
// TODO: Implement this function
if (numerator <= 0 || denominator <= 0) {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does the numerator be bigger than 0?

Comment on lines +31 to +44
if (!validRank.includes(rank) || !validSuit.includes(suit)) {
throw new Error("Invalid Card");
}

if (rank === "A") {
return 11;
}
else if (rank === "J" || rank=== "Q" || rank === "K") {
return 10;
}

// The line below allows us to load the getCardValue function into tests in other files.
// This will be useful in the "rewrite tests with jest" step.
module.exports = getCardValue;
else if (rank >= 2 && rank <= 10) {
return Number(rank);
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The indentation is a bit off. How can you ensure consistent formatting in your code?

Comment on lines +28 to +29
const validRank = ["A","2","3","4","5","6","7","8","9","10","J","Q","K"];
const validSuit = ["♠","♥","♦","♣"];

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job on explicitly listing all allowed ranks and suits. This makes the code easier to read and the logic for checking easier as well.

// The line below allows us to load the getCardValue function into tests in other files.
// This will be useful in the "rewrite tests with jest" step.
module.exports = getCardValue;
else if (rank >= 2 && rank <= 10) {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens if the condition is false?

expect(getCardValue("K♦")).toEqual(10);
});
});
describe("Invalid Cards", () => {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which part of the condition is not covered by the invalid test cases yet?
if (!validRank.includes(rank) || !validSuit.includes(suit)) {

@Luro91 Luro91 added Reviewed Volunteer to add when completing a review with trainee action still to take. and removed Needs Review Trainee to add when requesting review. PRs without this label will not be reviewed. labels Jul 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Reviewed Volunteer to add when completing a review with trainee action still to take.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants