Skip to content

June | Oct2025-1 | Structuring and Testing Data | Sprint 3 | Coursework - #3

Open
juneMonton wants to merge 11 commits into
mainfrom
coursework/sprint-3
Open

June | Oct2025-1 | Structuring and Testing Data | Sprint 3 | Coursework#3
juneMonton wants to merge 11 commits into
mainfrom
coursework/sprint-3

Conversation

@juneMonton

Copy link
Copy Markdown
Owner

Learners, PR Template

Self checklist

  • I have committed my files one by one, on purpose, and for a reason
  • I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title
  • I have tested my changes
  • My changes follow the style guide
  • My changes meet the requirements of this task

Changelist

This PR is for Sprint-3 Testing answers

Questions

Please guide me on regarding testing, when and how was it used in real working environment

@juneMonton
juneMonton requested a review from klaryon December 22, 2025 21:09

@nsi88 nsi88 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

It looks good overall. Left some rather minor comments. But would be good to at least checking the comments before merging. Will mark as "request changes"

// =============> write your explanation here : str has been declared in the function parameter and inside the function
// =============> write your new code here
function capitalise(str) {
return str `${str[0].toUpperCase()}${str.slice(1)}`;

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 syntax in here doesn't seem valid. Is it intentional?


function isProperFraction(numerator, denominator) {
if (numerator < denominator) return true;
if (Math.abs(numerator)< denominator) return true;// Use absolute value for negative numerators

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Do we need to handle the case with negative denominator?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

if (condition) { return true } else { return false } is considered a "bad taste" in programming.
It's better to write return condition in this case


// Handle Ace (A)
// Given a card with rank "A", return 11
if (rank === "A") return 11;

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I recommend to use auto-formatting. Otherwise the indentations are all over the place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants