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

Close test runner and Vitest shim gaps found in the 0.14 docs audit

Open
  • Is something wrong?
#1,278 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
testing-qa

Research direction

Start with docs/testing-api.md and reproduce the listed GocciaTestRunner, runTests, describe.todo, mock, and vi-member cases. Trace the test-runner and Vitest-shim entry points involved in each failure. Done means all listed behaviors match the --help text, documentation, or pinned Vitest behavior.

Written by the indexing model from the issue text.

Description

runtime

Summary

Test runner and Vitest-shim gaps. Found in the 0.14.0 docs audit.

Current behavior

  • --describe-timeout fires only while the describe callback itself runs. When it fires, later top-level tests in the file never run (Run Tests: 0), which contradicts --help's "aborts the suite and continues".
  • Inline snapshots with a bare file name. GocciaTestRunner user.test.js fails with Snapshot finalization failed: Cannot create empty directory; ./user.test.js works.
  • runTests({ showTestResults: false }) still prints the per-test ❌ lines.
  • describe.todo is undefined, although Vitest has it.
  • Mocks can't be constructed. A mock() can't be called with new (TypeError: C is not a constructor), and mock.instances is always [].
  • Missing vi members. vi.isMockFunction, vi.mockObject, vi.dynamicImportSettled and vi.defineHelper are absent, so calling them fails with a generic "is not a function" error rather than the shim's named unsupported-member error.

Expected behavior

Each behaves as its --help text and docs/testing-api.md describe, or matches the pinned Vitest behaviour.

Scope notes

docs/testing-api.md is being updated to describe the current behaviour.

Dominant language
Pascal
Stars
20
Forks
3
Avg merge
3d 17h
Merged PRs (30d)
53

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 frostney/GocciaScript

All issues in frostney/GocciaScript

Similar issues

More Testing & QA issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.