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

Skipped tests are shown in cli report within test execution

Open
#4,529 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, playwright
Domain
cli, testing

Research direction

Start by reproducing the CLI report with the shown mocha reporter configuration, especially verbose and features enabled, using the listed CodeceptJS, Node.js, and Playwright versions. Compare the report output with the requested behavior; done means passed and failed tests remain visible while skipped tests are omitted.

Written by the indexing model from the issue text.

Description

What are you trying to achieve?

In cli within test execution to see only passed/failed tests

What do you get instead?

While test execution except passed/failed tests, skipped tests also displayed that make track execution more difficult

Screenshot 2024-10-27 at 10 31 37

Details
  • CodeceptJS version: 3.6.5
  • NodeJS Version: 20
  • Operating System: Mac/Linux
  • playwright: 1.38.1
  • Configuration file:
    /** Mocha reporter */
    mocha: {
        reporterOptions: {
            "codeceptjs-cli-reporter": {
                stdout: "-",
                options: {
                    verbose: true,
                    features: true,
                }
            },
            "mocha-junit-reporter": {
                stdout: "-",
                options: {
                    mochaFile: 'output/result.[hash].xml',
                    includePending: false,
                }
            }
        }
    },
Dominant language
JavaScript
Stars
4.2k
Forks
756
Avg merge
2d 9h
Merged PRs (30d)
16

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 codeceptjs/CodeceptJS

All issues in codeceptjs/CodeceptJS

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.