Skip to content

test: add fast Vitest unit suite #135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Meir017 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

test: add fast Vitest unit suite #135

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8fdcc44
test: add fast Vitest unit suite
Meir017-msft Jun 16, 2026
40c9ad9
test: split unit and integration suites
Meir017-msft Jun 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .github/workflows/e2e.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,12 @@ jobs:
- name: Install dependencies
run: npm install

- name: Run unit tests
run: npm run test:unit

- name: Run integration tests
run: npm run test:integration

- name: Package tmax for e2e
run: npm run package

Expand Down
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ For larger ideas, open an issue first to discuss the shape of the change before
2. Set up the dev environment (see [Building from Source](README.md#building-from-source)) and run `npm start` to verify the app launches.
3. Make your change. Keep PRs focused - one feature or fix per PR.
4. **Cross-platform compatibility is required.** tmax ships on Windows, macOS, and Linux. Use `isMac ? event.metaKey : event.ctrlKey` for primary modifiers, `formatKeyForPlatform()` for shortcut text in the UI, and avoid hardcoded paths or shell assumptions. See [`CLAUDE.md`](CLAUDE.md) for the full guidelines.
5. Run the e2e test suite: `npm run test:e2e`. Add a Playwright spec under `e2e/` for any user-visible bug fix or new feature.
5. Run the fast unit suite with `npm test`; run `npm run test:integration` for filesystem/git/CLI behavior; run the Electron e2e suite with `npm run test:e2e` for user-visible app behavior. Add unit tests under `tests/unit/` for pure logic, integration tests under `tests/integration/` for external boundaries, and Playwright specs under `tests/e2e/` for UI/Electron flows.
6. Open the PR with a description of what changed and why, plus any UI screenshots.

## Code style
Expand Down
Loading