Verifying components relying on tabster through unit tests

Open
#280 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
accessibility, testing-qa

Research direction

Start with the Fluent 9 Popover focus behavior described in the issue and compare what can be observed in Storybook with assertions in Jest and jsdom. Check whether Tabster behavior can be verified in that environment; if not, determine whether the expected coverage belongs in browser-based end-to-end tests. Done means documenting a supported test approach or clearly identifying the required e2e coverage.

Written by the indexing model from the issue text.

Description

Hey folks,

I am using Fluent 9 Popover and wanted to verify that correct element is focused open opening the Popover. For the component I created, I can visually verify in Storybook that correct element is focused. However, when I want to make such assertion in unit tests, it seems to no longer be the case. Can tabster functionality be somehow verified in jest and jsdom environment? Or the only way to verify is to have e2e tests, rendering browser window?

Dominant language
TypeScript
Stars
165
Forks
42
Avg merge
1d 11h
Merged PRs (30d)
9

Contributor guide

Open the contributing guide

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 microsoft/tabster

All issues in microsoft/tabster

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.