[Clock] Review Test Cases and Discuss Structure and Objectives of Exercise

Open
#3,012 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

Start by reviewing the Clock exercise's current instructions and tests, then read issues #2926 and #3008 for the reported concerns. Done means the exercise's structure, objectives, tests, directions, and hints have an agreed revision plan that addresses the discussion.

Written by the indexing model from the issue text.

Description

discussion 💬

Filing this as a tracking issue and invitation to a discussion on revisions to this exercise.

The intent of Clock was to practice class customization and operator overloading via dunder methods in Python.
We've recently had quite a few changes, adding __repr__ to the mix, as well as additional instructions and tests in support of that change. A few issues have now come up around it:

  1. Issue #2926
  2. Issue #3008

It feels like this exercise is overloaded. It especially has too many tests, and is perhaps not clear enough in its directions and hints as to what the student does or does not need to think about for their implementations.

Thoughts on rework/adjustment clarification strategies welcome here.

Dominant language
Python
Stars
2.5k
Forks
1.5k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from exercism/python

All issues in exercism/python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.