You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`npm run build` — Build with `rslib` (use `build:local` for sourcemaps).
16
16
-`npm run watch` — Rebuild on change.
@@ -19,25 +19,25 @@ Concise contributor guide for the Rstest VS Code extension package.
19
19
-`npm run test:e2e` — Compile tests and run VS Code Extension Host E2E (downloads VS Code on first run).
20
20
-`npm run lint` — Run Biome checks.
21
21
22
-
## Coding Style & Naming Conventions
22
+
## Coding style & naming conventions
23
23
24
24
- Language: TypeScript, 2-space indentation. Keep changes minimal and focused.
25
25
- Naming: camelCase for files and symbols; PascalCase for classes; follow existing patterns (e.g., `testTree.ts`, `parserTest.ts`).
26
26
- Linting: Biome (`npm run lint`). Prefer simple, readable logic over cleverness.
27
27
28
-
## Testing Guidelines
28
+
## Testing guidelines
29
29
30
30
- Name tests `*.test.ts`. Place parser/unit tests in `tests/unit/**`; E2E tests in `tests/suite/**` (loaded by the E2E runner only).
31
31
- E2E opens `tests/fixtures` workspace automatically; use `toLabelTree()` from `tests/suite/index.test.ts` for stable tree assertions.
32
32
- Typical loop: `npm run typecheck` → `npm run test:unit` → `npm run test:e2e`.
33
33
34
-
## Commit & Pull Request Guidelines
34
+
## Commit & pull request guidelines
35
35
36
36
- Write clear, imperative commit messages; keep PRs small and scoped. Reference issues (e.g., `Fixes #123`).
37
37
- Include rationale, testing notes, and screenshots/logs if relevant (e.g., label trees, error output).
38
38
- Avoid unrelated refactors; update or add tests with behavior changes.
39
39
40
-
## Architecture Overview
40
+
## Architecture overview
41
41
42
42
- Two-process design: VS Code extension (`extension.ts`) communicates with a worker (`worker/index.ts`) via WebSocket. Main sends `WorkerInitData`/`WorkerRunTestData`; worker emits `WorkerEventFinish`.
|`rstest.testFileGlobPattern`| string[]| Resource |`["**/*.test.*", "**/*.spec.*"]`| Glob pattern(s) used to discover test files in the workspace. |
21
21
22
-
## How it Works
22
+
## How it works
23
23
24
24
- On activation, the extension scans for test files using `rstest.testFileGlobPattern` and creates a Test Explorer tree.
25
25
- File system watchers keep the tree synchronized as files are created, modified, or deleted.
@@ -35,11 +35,12 @@ Common commands (run from this package):
35
35
-`npm run test:unit` — Unit tests via Rstest
36
36
-`npm run test:e2e` — VS Code Extension Host E2E tests
37
37
38
-
### Packaging & Publishing
38
+
### Packaging & publishing
39
39
40
40
- Local package (current platform): `npm run package:vsix`
41
41
- Publish (current platform): `npm run publish:vsce` (requires `VSCE_PAT`)
42
42
43
43
CI
44
+
44
45
- On tag push or manual dispatch, GitHub Actions runs on Linux and publishes for all platforms using `vsce publish --target` (win32/darwin/linux; x64 and arm64).
45
46
- Configure the `VSCE_PAT` repository secret for Marketplace publishing.
0 commit comments