Summary
The project has largely moved to Playwright for E2E testing (101 tests across 14 spec files), but 9 Selenide tests remain in 2 test classes with 12 supporting page objects and utilities.
Selenide files to migrate
Test classes (9 tests):
src/test/java/com/digitalsanctuary/spring/demo/user/ui/SpringUserFrameworkUiTest.java (5 tests)src/test/java/com/digitalsanctuary/spring/demo/user/ui/CompleteUserJourneyE2ETest.java (4 tests)
Page objects & utilities to remove after migration:
- 12 Page Object classes (LoginPage, RegisterPage, ForgotPasswordPage, etc.)
- 2 Utility classes (DatabaseStateValidator, EmailVerificationSimulator)
- 1 Base test class (BaseUiTest)
After migration
- Remove
com.codeborne:selenide dependency from build.gradle
- Remove
uiTest Gradle task if no longer needed
- Update CLAUDE.md to remove "Legacy UI tests with Selenide" line
Why
Consolidating on a single E2E framework reduces maintenance overhead, simplifies CI, and avoids contributors needing to learn two test frameworks.
Summary
The project has largely moved to Playwright for E2E testing (101 tests across 14 spec files), but 9 Selenide tests remain in 2 test classes with 12 supporting page objects and utilities.
Selenide files to migrate
Test classes (9 tests):
src/test/java/com/digitalsanctuary/spring/demo/user/ui/SpringUserFrameworkUiTest.java(5 tests)src/test/java/com/digitalsanctuary/spring/demo/user/ui/CompleteUserJourneyE2ETest.java(4 tests)Page objects & utilities to remove after migration:
After migration
com.codeborne:selenidedependency frombuild.gradleuiTestGradle task if no longer neededWhy
Consolidating on a single E2E framework reduces maintenance overhead, simplifies CI, and avoids contributors needing to learn two test frameworks.