Eliminate implementation-specific tests

Open
#150 2 comments 1 reaction 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
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
clojure
Domain
testing

Research direction

Review the tests throughout @exercism/clojure and its related examples, starting with the robot-names exercise test discussed in #149 and #148. Check whether each test verifies observable functionality rather than behavior of a particular stateful construct. Done means the test suite has been reviewed and implementation-specific expectations have been removed or revised.

Written by the indexing model from the issue text.

Description

testing

Inspired by a review of #149 (fix for #148) - a new test was failing based on a (IMHO) poorly constructed state atom in the robot-names exercise example; one of the beauties of Clojure, and, a fortiori, testing in Clojure is being able to test pure functions with pure functions, rather than relying on underlying implementation details for mutable state.

This issue calls for a review of all tests in @exercism/clojure and there related examples to ensure that tests only check for functionality without relying on the behavior of particular stateful constructs to pass.

Dominant language
Clojure
Stars
177
Forks
159
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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/clojure

All issues in exercism/clojure

Similar issues

More Clojure issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.