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

Run Selected/Failed Tests or combine Tests which doesn't fall under a pattern

Open
#2,776 0 comments 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
javascript, node.js
Domain
cli, testing-qa

Research direction

Start by tracing the run and run-workers command handling for the proposed --rerun-test option, then inspect how failedCases.json would be created, read, updated, validated, and removed. Done means rerunning selected or failed files, reporting invalid or missing entries, supporting files from different folders, and clearing the file when the final execution passes.

Written by the indexing model from the issue text.

Description

What are you trying to achieve?

Adding new option to run and run-workers to rerun the failed tests or the selected tests. Option added in --rerun-tests.

Working Nature :

  • When the run is initiated and when script(s) fail, the test script will be added in failedCases.json file.
  • When the rerun is initiated with the run --rerun-test or run-workers 2 --rerun-test command, test files will be picked from the json file instead of the config file.
  • Failed Tests will be updated from the last execution regardless of the mode it ran(either run or run --rerun-tests)
  • When all the tests are passed in the last execution, failesCases.json file be deleted from the project folder.
  • We can add files from different folders, files which doesn't falls under a single pattern etc.
  • When a invalid files or files are provided in the json file, message will be thrown with the invalid file.
  • When there is no failedCases.json file or no tests in the failedCases.json file and the run is initiated, appropriate message will be displayed to the user.

Benefits :

  • If the failed scripts need to run against different environments, it could be accomplished with this approach.
  • You can create failedCases.json manually and run the specific scripts you want to execute using the above commands.
  • This would be much useful, if you want to run the scripts which doesn't come under a pattern and from test files from different folders.

Console Outputs :

Failed Scripts when run-workers

1 Worker Failed Scripts

Failed Worker Script In Failed Cases

2 Failed Worker Script In Failed Cases JSON

Rerun Of the Failed Script

3 Rerun Of the Failed Script

Failed Cases JSON removed after the Failed Script succeeded

4 Failed Cases JSON removed after the Failed Script succeeded

Retries Captured In Allure

5 Retries Captured In Allure

Invalid Files Identification

Invalid Files Identification

Running Files From Two Different Folder

Running Files From Two Different Folder

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.