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

Run Tests Locally

Open
  • Is something wrong?
#204 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
testing, tooling

Research direction

Start by inspecting the existing configuration that runs tests when a pull request is merged and identify the current commands for all tests, dev-time tests, and run-time tests. Add local commands that write comparison output to temporary files; done means all three categories run locally without changing tracked files, with framework filtering treated as optional.

Written by the indexing model from the issue text.

Description

good first issue

Tests run on merge to PR, but it would be great if we had three simple commands to run locally.

It would be great that these save to temp files for comparison rather than the actual files we use.

We need a script for:

  • Running all tests
  • Running all dev time tests
  • Running all run times tests

A final nice to have would be to filter by framework

Dominant language
TypeScript
Stars
42
Forks
16
Avg merge
13h 28m
Merged PRs (30d)
149

Getting set up

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 e18e/framework-tracker

All issues in e18e/framework-tracker

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.