Skip to content

Conversation

@oidacra
Copy link
Member

@oidacra oidacra commented Sep 12, 2025

  • Updated Jest configuration to include coverage reporters and JUnit output.
  • Introduced Playwright configuration for different environments (dev, ci, local) with headless options.
  • Added new components and locators for better test organization.
  • Implemented login functionality and various test cases for login scenarios, including valid and invalid credentials.
  • Created environment configuration for managing base URLs and server reuse.
  • Added utility functions for waiting on locators and generating base64 credentials.

This update improves the structure and reliability of end-to-end tests for the dotCMS UI.

@github-actions
Copy link

❌ Issue Linking Required

This PR could not be linked to an issue. All PRs must be linked to an issue for tracking purposes.

How to fix this:

Option 1: Add keyword to PR body (Recommended - auto-removes this comment)
Edit this PR description and add one of these lines:

  • This PR fixes #123 or Fixes: #123

  • This PR closes #123 or Closes: #123

  • This PR resolves #123 or Resolves: #123

  • Other supported keywords: fix, fixed, close, closed, resolve, resolved
    Option 2: Link via GitHub UI (Note: won't clear the failed check)

  1. Go to the PR → Development section (right sidebar)

  2. Click "Link issue" and select an existing issue

  3. Push a new commit or re-run the workflow to clear the failed check
    Option 3: Use branch naming
    Create a new branch with one of these patterns:

  • 123-feature-description (number at start)

  • issue-123-feature-description (issue-number at start)

  • feature-issue-123 (issue-number anywhere)

Why is this required?

Issue linking ensures proper tracking, documentation, and helps maintain project history. It connects your code changes to the problem they solve.---

This comment was automatically generated by the issue linking workflow

@oidacra oidacra changed the title feat(dotcms-ui-e2e): enhance end-to-end testing setup and add new test cases feat(dotcms-ui-e2e): Make run E2E inside Nx Sep 15, 2025
@oidacra oidacra marked this pull request as draft September 19, 2025 13:38
@oidacra oidacra requested review from nicobytes and zJaaal September 19, 2025 20:07
"update": "nx migrate latest",
"workspace-generator": "nx workspace-generator",
"help": "nx help"
"test:dotcms:ci": "../mvnw -pl :dotcms-core-web test"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes the Docker image local

@semgrep-code-dotcms-test
Copy link

Legal Risk

The following dependencies were released under a license that
has been flagged by your organization for consideration.

Recommendation

While merging is not directly blocked, it's best to pause and consider what it means to use this license before continuing. If you are unsure, reach out to your security team or Semgrep admin to address this issue.

MPL-2.0

…t cases

- Updated Jest configuration to include coverage reporters and JUnit output.
- Introduced Playwright configuration for different environments (dev, ci, local) with headless options.
- Added new components and locators for better test organization.
- Implemented login functionality and various test cases for login scenarios, including valid and invalid credentials.
- Created environment configuration for managing base URLs and server reuse.
- Added utility functions for waiting on locators and generating base64 credentials.

This update improves the structure and reliability of end-to-end tests for the dotCMS UI.
… components

- Added new script for code generation in Playwright.
- Updated README with critical data management guidelines for E2E tests.
- Introduced new components and locators for improved test organization.
- Implemented new page classes for content type management and listing.
- Refactored existing components to utilize more stable selectors.
- Removed outdated locator files to streamline the codebase.

This update improves the structure and reliability of end-to-end tests for the dotCMS UI.
…Docker support

- Refactored end-to-end testing scripts to utilize new commands for CI and development environments.
- Introduced a new Docker Compose configuration for PostgreSQL, Elasticsearch, and WireMock services to facilitate testing.
- Updated project.json to streamline environment configurations and enhance test execution.
- Added health checks for Docker services to ensure reliability during tests.
- Added reporters to Jest configuration files for improved test reporting.
- Changed console.log to console.warn in Playwright configuration for better logging.
- Updated import paths in several files to ensure consistency and correctness.
- Refactored login page navigation logic to wait for URL stability instead of a fixed timeout.
@github-actions
Copy link

This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale label Oct 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant