Skip to content

test(react): migrate test environment from Playwright to jsdom#234

Open
Kavidu23 wants to merge 5 commits intoasgardeo:mainfrom
Kavidu23:test/react-jsdom-migration
Open

test(react): migrate test environment from Playwright to jsdom#234
Kavidu23 wants to merge 5 commits intoasgardeo:mainfrom
Kavidu23:test/react-jsdom-migration

Conversation

@Kavidu23
Copy link

@Kavidu23 Kavidu23 commented Nov 6, 2025

Purpose

This PR refactors the @asgardeo/react package test configuration to use the jsdom environment instead of Playwright’s browser-based setup.
The migration improves CI reliability, reduces dependency overhead, and ensures consistent test behavior across local and cloud environments.

Key highlights:

Removed Playwright test configuration and dependencies.

Updated vitest.config.ts to use jsdom for headless testing.

Cleaned up unused screenshot files and cache references.

Verified alignment with @asgardeo/tanstack-router test setup.

Confirmed all tests pass locally.

Related Issues

N/A

Related PRs

#220 — Adds unit tests for @asgardeo/react hooks.

Checklist

Followed the CONTRIBUTING
guidelines.

Manual test round performed and verified.

Documentation provided. (N/A)

Unit tests provided and verified locally.

Security checks

Followed secure coding standards in WSO2 Secure Engineering Guidelines
.

Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.

- Replaced Playwright browser testing config with Vitest jsdom environment - Removed unnecessary screenshots and Playwright setup - Simplified test configuration to match other packages and ensure CI compatibility
- replaced Playwright browser config with Vitest jsdom - removed unused screenshots and Playwright dependencies - aligned React package test setup with other modules for CI stability
@asgardeo-github-bot
Copy link

⚠️ No Changeset found

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go.

If these changes should result in a version bump, you need to add a changeset.

Refer Release Documentation to learn how to add a changeset.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants