Address tests skipped during vitest migration

[cameronjoyner]

In a coming series of PRs we're switching from Karma to Vitest. In the pursuit of that change we're going to be faced with tests that don't translate 1:1. Our options are either to delete, modify expectations or to selectively move to an alternative like Playwright.

[cameronjoyner]

In #7721 I laid the ground work for the broader vitest migration. At that time I had to skip 3 tests in order to pass CI checks

Overlay Focus Management Tests

These tests were skipped as part of the @testing-library/user-event v14 upgrade. The underlying Blueprint behavior remains valid; only the test mechanisms are incompatible with the new testing library version.

File	Test Name	Reason	Remediation
overlayTests.tsx:426	"does not crash while trying to return focus to overlay if user clicks outside the document"	@testing-library/user-event v14 installs a global focus listener that crashes when event.target is not a DOM element. This test dispatches a focus event with window as the target to simulate clicking browser chrome.	Delete or move to Playwright browser tests
overlay2Tests.tsx:472	"should return focus to overlay after clicking an outside element if enforceFocus=true"	jsdom + requestAnimationFrame timing issue. The enforceFocus mechanism uses RAF to delay focus manipulation, and RAF timing in jsdom is inconsistent with userEvent clicks.	Delete or move to Playwright browser tests
overlay2Tests.tsx:607	"should not crash while trying to return focus to overlay if user clicks outside the document"	Same as first entry - @testing-library/user-event v14's global focus listener crashes on non-DOM element targets.	Delete or move to Playwright browser tests

[cameronjoyner]

Skipped Tests in @blueprintjs/core (cj/vitest-core branch)

This document catalogs tests that were skipped during the vitest migration. The underlying Blueprint behavior remains valid in all cases; only the test mechanisms are incompatible with jsdom or the new testing library configuration.

---

Overlay Focus Management Tests

These tests were skipped as part of the @testing-library/user-event v14 upgrade. The underlying Blueprint behavior remains valid; only the test mechanisms are incompatible with the new testing library version.

File	Test Name	Reason	Remediation
overlayTests.tsx:426	"does not crash while trying to return focus to overlay if user clicks outside the document"	@testing-library/user-event v14 installs a global focus listener that crashes when event.target is not a DOM element. This test dispatches a focus event with window as the target to simulate clicking browser chrome.	Delete or move to Playwright browser tests
overlayTests.tsx:538	"lifecycle methods called as expected"	Uses enzyme's setProps() to toggle isOpen and relies on sleep() to wait for CSSTransition lifecycle callbacks. Enzyme's setProps() with RTG transitions is unreliable in vitest's jsdom environment.	Rewrite using @testing-library/react's rerender() or move to Playwright
overlay2Tests.tsx:473	"should return focus to overlay after clicking an outside element if enforceFocus=true"	jsdom + requestAnimationFrame timing issue. The enforceFocus mechanism uses RAF to delay focus manipulation, and RAF timing in jsdom is inconsistent with userEvent clicks.	Delete or move to Playwright browser tests
overlay2Tests.tsx:608	"should not crash while trying to return focus to overlay if user clicks outside the document"	Same as overlayTests.tsx:426 — @testing-library/user-event v14's global focus listener crashes on non-DOM element targets.	Delete or move to Playwright browser tests

---

OverflowList Tests (Entire Suite Skipped)

File	Test Name	Reason	Remediation
overflowListTests.tsx:40	describe.skip("<OverflowList>") (entire suite)	Tests rely on DOM measurement (getBoundingClientRect, ResizeObserver, container width changes) which jsdom does not support. The component uses resize observers and real layout calculations.	Move entire suite to Playwright browser tests

---

Breadcrumbs Tests

File	Test Name	Reason	Remediation
breadcrumbsTests.tsx:67	"should render the correct overflow menu items"	Depends on <OverflowList> measurement behavior which jsdom cannot simulate. The test sets a container width and expects overflow calculations to produce specific menu items.	Move to Playwright browser tests (depends on OverflowList fix)
breadcrumbsTests.tsx:80	"should render the correct overflow menu items when collapsing from END"	Same as above — depends on OverflowList measurement with collapseFrom={Boundary.END}.	Move to Playwright browser tests (depends on OverflowList fix)

---

TextArea Tests

File	Test Name	Reason	Remediation
textAreaTests.tsx:64	"resizes with long text input when autoResize enabled"	jsdom doesn't compute real scrollHeight values. The autoResize feature relies on comparing scrollHeight before and after text changes.	Move to Playwright browser tests

---

Text Tests

File	Test Name	Reason	Remediation
textTests.tsx:78	"adds the title attribute when text overflows"	jsdom doesn't compute real overflow measurements. The component uses scrollWidth > clientWidth to detect overflow and conditionally add a title attribute.	Move to Playwright browser tests

---

Icon Tests

File	Test Name	Reason	Remediation
iconTests.tsx:61	"renders icon name"	The assertIconHasPath helper relies on async icon loading and path verification that is timing-sensitive in vitest.	Investigate async loading behavior; may need waitFor or act() wrapping

---

Slider Tests

These tests use enzyme's simulate() for mouse events and rely on getBoundingClientRect() for track width calculations, neither of which work reliably in jsdom.

File	Test Name	Reason	Remediation
sliderTests.tsx:48	"renders primary track segment between initialValue and value"	Uses getBoundingClientRect().width which returns 0 in jsdom.	Move to Playwright browser tests
sliderTests.tsx:56	"renders primary track segment between initialValue and value when value is less than initial value"	Same as above — relies on getBoundingClientRect().width.	Move to Playwright browser tests
sliderTests.tsx:81	"moving mouse calls onChange with nearest value"	Uses simulateMovement() helper that dispatches mouse events. Enzyme mouse event simulation doesn't update component state correctly in vitest/jsdom.	Move to Playwright browser tests
sliderTests.tsx:92	"releasing mouse calls onRelease with nearest value"	Same as above — relies on mouse event simulation via simulateMovement().	Move to Playwright browser tests
sliderTests.tsx:102	"disabled slider never invokes event handlers"	Same as above — relies on mouse event simulation and keyboard events.	Move to Playwright browser tests

---

RangeSlider Tests

File	Test Name	Reason	Remediation
rangeSliderTests.tsx:46	"renders primary track segment between two values"	Uses getBoundingClientRect().width which returns 0 in jsdom.	Move to Playwright browser tests

---

MultiSlider Tests

File	Test Name	Reason	Remediation
multiSliderTests.tsx:53	"handle values are automatically sorted"	Uses enzyme's simulate("mousedown") which doesn't trigger real event handlers in vitest/jsdom.	Move to Playwright browser tests
multiSliderTests.tsx:72	"moving mouse on the first handle updates the first value"	Uses simulateMovement() helper for mouse drag simulation.	Move to Playwright browser tests
multiSliderTests.tsx:88	"moving mouse on the middle handle updates the middle value"	Same as above — relies on mouse drag simulation.	Move to Playwright browser tests
multiSliderTests.tsx:109	"moving mouse on the last handle updates the last value"	Same as above — relies on mouse drag simulation.	Move to Playwright browser tests
multiSliderTests.tsx:130	"releasing mouse on a track value closer to the first handle moves the first handle"	Uses enzyme's simulate("mousedown") on track element.	Move to Playwright browser tests
multiSliderTests.tsx:137	"releasing mouse on a track value slightly below the middle handle moves the middle handle"	Same as above.	Move to Playwright browser tests
multiSliderTests.tsx:144	"releasing mouse on a track value slightly above the middle handle moves the middle handle"	Same as above.	Move to Playwright browser tests
multiSliderTests.tsx:151	"releasing mouse on a track value closer to the last handle moves the last handle"	Same as above.	Move to Playwright browser tests
multiSliderTests.tsx:158	"when values are equal, releasing mouse on a track still moves the nearest handle"	Same as above — relies on mouse click simulation on track.	Move to Playwright browser tests

---

Summary by Category

Category	Count	Primary Issue
DOM Measurement (getBoundingClientRect, overflow, scrollHeight)	11	jsdom returns 0 for all layout measurements
Mouse Event Simulation (drag, click on specific coordinates)	14	Enzyme's simulate() doesn't trigger real React event handlers in vitest
Focus Event Edge Cases	3	@testing-library/user-event v14 global listener conflicts
Async/Timing (RAF, transitions)	2	jsdom RAF timing inconsistent with userEvent
Total	30

---