Cape Town | 2026-ITP-Jan | Isaac Abodunrin | Sprint 3 | Implement and Rewrite Tests Coursework

[bytesandroses]

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

Implemented solutions to the following, using console.assert() for basic testing:

• 1-get-angle-type.js
• 2-is-proper-fraction.js
• 3-get-card-value.js

Rewrite tests for the solutions above using Jest

[cjyuan]

Very thorough tests! Well done!

[cjyuan]

Isn't 0/1 a proper fraction?

[bytesandroses]

Good catch -- you're absolutely right since the definition of a proper fraction is where the magnitude of the denominator is great than that of the numerator. It doesn't say the numerator can't be zero, so I've updated the code to correct this

[cjyuan]

With this way of expressing the test, the test description
Should return ${rank} when given a card ${cardFace}
would appear 36 times on the console (with different ranks and suits).

Should you need to reduce the number of messages on the console, you can consider grouping similar test cases under one category as

test(`Should return the numerical value of number cards`, () => {
  const cardsNumbers = [2, 3, 4, 5, 6, 7, 8, 9, 10];
  for (const rank of cardsNumbers) {
    for (const suit of suits) {
      const cardFace = `${rank}${suit}`;
      expect(getCardValue(cardFace)).toEqual(rank);
    }
  }
}

[bytesandroses]

Thanks for the tip. I've refactored it so that similar test cases use one category -- there are a lot fewer printouts in the console now