Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Investigate running the test suite without all tests in CI

Open
#236 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp

Research direction

Start with the root CMakeLists file and the test suite setup described in the issue, then inspect how EXERCISM_RUN_ALL_TESTS controls compilation. Verify whether each test suite can compile and run without that definition, and confirm that CI exercises those targets successfully.

Written by the indexing model from the issue text.

Description

enhancement good first patch help wanted

This was brought up in #234.

It would seem that at least the one test suite wouldn't compile without defining EXERCISM_RUN_ALL_TESTS, as the test suite used a global variable that was unused on the first test and everything else was #ifdef'd out. We should consider modifying the root CMakeLists file to compile a new test target for every test without that defined just to make sure we still pass the tests. It's a bad experience if they can't use just the initial test in the test suite.

Dominant language
C++
Stars
291
Forks
244
Avg merge
17m
Merged PRs (30d)
1

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

All issues in exercism/cpp

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.