harvester-ui-extension/docs/agents.md/contributors/2_unit-tests.md at 71141b257ac7d96b3c68566366a0fefb42798d1f

mirror of https://github.com/harvester/harvester-ui-extension.git synced 2026-10-14 10:06:04 +08:00

Files

T

Volker Theile 71141b257a feat: Add a unit test target (jest) to the UI extension and run it in CI (#1192 )

- Introduce test targets.
- Adding additional tests.

Related to: https://github.com/harvester/harvester/issues/11892

Signed-off-by: Volker Theile <vtheile@suse.com>

2026-10-13 18:00:38 +02:00

1.1 KiB

Raw Blame History

Unit Tests (Jest)

Unit and component tests run with Jest. The setup follows the Rancher dashboard and the Rancher extension template (rancher/ui-plugin-examples), so both stay aligned.

Run the tests in watch mode with yarn test, all tests once with yarn test:ci, a single file with yarn test <path>. CI runs yarn test:ci on every pull request.
Test files live next to the code in __tests__ folders and are named <name>.test.js or <name>.test.ts.
Configuration:
- jest.config.js: environment, module aliases (@shell, @components, @pkg) and transforms.
- jest.setup.js: global mocks (t, $store, common directives) and browser APIs that jsdom does not provide.
- vue3JestRegisterTs.js: makes TypeScript available to the Vue compiler, otherwise .vue files with typed props fail to compile.
Components are tested with the Vue Test Utils 2 API: use props and global.mocks, not the Vue 2 options propsData and mocks.
Models and utils can be tested without mounting anything, see pkg/harvester/models/__tests__ for examples.

1.1 KiB Raw Blame History

Unit Tests (Jest)

1.1 KiB

Raw Blame History