Nightly E2E Tests - Node Suite Failing with Multiple Playwright Test Timeouts

[spbolton]

Description

The nightly E2E Tests - Node Suite is failing consistently due to multiple Playwright test timeouts, indicating critical issues with the UI test environment or application performance under CI conditions.

Acceptance Criteria

• [Define what needs to be accomplished]

Additional Notes

[Any additional context or notes]

[spbolton]

Detailed Failure Analysis

Specific Test Failures from Log Analysis

1. Login Button Disabled Issue

• Test: - 'should display the page in the pages list'
• Location:
• Error: Login button () remains disabled throughout 40-second timeout
• Attempts: 80+ retry attempts with 500ms intervals
• Impact: Prevents any test requiring authentication from proceeding

2. Workflow Execution Timeout

• Test: - 'Delete a file asset content'
• Location:
• Error: Waiting for 'Workflow executed' message in iframe timeout
• Target: iframe[name="detailFrame"].contentFrame().getByText('Workflow executed')
• Duration: 40,000ms timeout exceeded

Test Summary Results

Build Failure Stack Trace

Environment Details

• Runner: ubuntu-24.04 (Version: 20250831.1.0)
• Total Build Time: 18:11 minutes
• Maven Goal: verify -De2e.test.skip=false -De2e.test.env=ci -pl :dotcms-e2e-node
• Yarn Command: yarn run start-ci

Reproduction Commands

yarn run v1.22.22
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
yarn run v1.22.22
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Next Investigation Steps

1. Compare CI vs Local: Run same tests locally to isolate CI-specific issues
2. Login Button State: Debug why submit button remains disabled in CI environment
3. Workflow Performance: Profile backend workflow execution times under CI load
4. Test Stability: Analyze patterns in the 4 flaky tests for common root causes

This appears to be a systematic issue with the CI test environment rather than isolated test failures.

[spbolton]

Complete E2E Test Failure Logs

I've analyzed the full GitHub Actions logs and created a comprehensive failure report. Here are the complete logs with detailed analysis:

📋 Click to view complete E2E test failure logs

GitHub Actions E2E Test Failure Logs
=====================================
Job: Nightly Test / E2E Tests - Node Suite
Run ID: 17538798460
Job ID: 49807476584
Date: 2025-09-08T03:46:14Z - 2025-09-08T04:10:44Z
Total Duration: 18:11 minutes

Environment Details:
- Runner: ubuntu-24.04 (Version: 20250831.1.0)
- Runner Version: 2.328.0
- Repository: dotCMS/core
- Commit: 4b3113db5f491060d5130b453892753b546d9f54
- Maven Args: verify -De2e.test.skip=false -De2e.test.env=ci -pl :dotcms-e2e-node
- MAVEN_OPTS: -Xmx2048m

=== TEST FAILURE SUMMARY ===
🎭 Playwright Run Summary:
1 failed
  [chromium] › components/breadcrumb.spec.ts:82:7 › Template page › should display correctly on the Template page

4 flaky  
  [chromium] › components/breadcrumb.spec.ts:50:5 › should display correctly on the Containers page
  [chromium] › contentSearch/contentEditing.spec.ts:40:5 › Add a new Generic content
  [chromium] › contentSearch/contentEditing.spec.ts:414:5 › Delete a file asset content
  [chromium] › pages/create-page.spec.ts:38:5 › should display the page in the pages list

2 skipped
45 passed (15.2m)

=== DETAILED FAILURE ANALYSIS ===

1. LOGIN BUTTON DISABLED ISSUE (Multiple Tests Affected)
Error: locator.click: Test timeout of 40000ms exceeded.
Element: <button disabled data-testid="submitButton" class="p-element login__button p-button p-component ng-star-inserted">
Location: e2e/dotcms-e2e-node/frontend/src/pages/login.page.ts:24:27
Issue: Submit button remains disabled throughout 40-second timeout with 80+ retry attempts

Affected Tests:
- components/breadcrumb.spec.ts:82:7 › Template page › should display correctly on the Template page
- components/breadcrumb.spec.ts:50:5 › should display correctly on the Containers page  
- pages/create-page.spec.ts:38:5 › should display the page in the pages list

Call Pattern:
- waiting for getByTestId('submitButton')
- locator resolved to <button disabled...>
- attempting click action
- waiting for element to be visible, enabled and stable
- element is not enabled
- retrying click action, attempt #1-80+
- waiting 500ms between attempts

2. WORKFLOW EXECUTION TIMEOUT
Test: contentSearch/contentEditing.spec.ts:414:5 › Delete a file asset content
Error: locator.waitFor: Test timeout of 40000ms exceeded
Target: iframe[name="detailFrame"].contentFrame().getByText('Workflow executed')
Location: e2e/dotcms-e2e-node/frontend/src/utils/utils.ts:12:17
Issue: Workflow processing not completing within expected timeframe

3. CONTENT TYPE SELECTION TIMEOUT  
Test: contentSearch/contentEditing.spec.ts:40:5 › Add a new Generic content
Error: locator.waitFor: Test timeout of 40000ms exceeded
Target: iframe[name="detailFrame"].contentFrame().getByLabel('structure_inode_popup')
Location: e2e/dotcms-e2e-node/frontend/src/utils/utils.ts:12:17
Issue: Content type selection popup not appearing

4. BREADCRUMB VALIDATION FAILURE
Test: components/breadcrumb.spec.ts:82:7 › Template page › should display correctly
Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected)
Expected: "Site ManagerTemplates"  
Received: "Getting Started"
Issue: Navigation state inconsistency - showing Getting Started instead of expected breadcrumb

=== BUILD FAILURE STACK TRACE ===
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.12.1:yarn (run node script) on project dotcms-e2e-node: Failed to run task: 'yarn run start-ci' failed. 
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.12.1:yarn (run node script) on project dotcms-e2e-node: Failed to run task
	at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:347)
	at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:330)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213)
...
Caused by: com.github.eirslett.maven.plugins.frontend.lib.TaskRunnerException: 'yarn run start-ci' failed.
	at com.github.eirslett.maven.plugins.frontend.lib.YarnTaskExecutor.execute (YarnTaskExecutor.java:64)
	at com.github.eirslett.maven.plugins.frontend.mojo.YarnMojo.execute (YarnMojo.java:65)

=== SLOW TEST WARNINGS ===
- contentSearch/portletIntegrity.spec.ts took 1.1m
- newEditContent/fields/textField.spec.ts took 47.0s  
- newEditContent/fields/siteOrFolderField.spec.ts took 43.9s
- pages/unpublish-page.spec.ts took 42.6s
- pages/archive-page.spec.ts took 40.2s

=== ROOT CAUSE ANALYSIS ===
1. PRIMARY ISSUE: Login button remains disabled preventing authentication flow
2. SECONDARY ISSUE: Backend workflow processing delays exceeding timeout thresholds
3. ENVIRONMENTAL: CI environment performance/timing differences from local development
4. FLAKINESS: Multiple tests showing intermittent timeout behaviors

=== RECOMMENDED INVESTIGATION ===
1. Login flow initialization - why submit button not enabling in CI
2. Backend performance under CI load conditions
3. Environment-specific configuration differences
4. Test stability improvements and timeout adjustments for CI environment

Key Findings:

1. Primary Root Cause: Login button () remains disabled throughout the entire 40-second timeout period, preventing any authentication-dependent tests from proceeding.

2. Secondary Issues:

   • Workflow execution timeouts (40s) when waiting for 'Workflow executed' messages
   • Content type selection popup not appearing in expected timeframes
   • Navigation breadcrumb state inconsistencies

3. Environment Impact: The CI environment appears to have performance/timing characteristics that differ significantly from local development, causing widespread test instability.

4. Test Flakiness Pattern: All 4 flaky tests share the common issue of UI elements not reaching expected states within timeout periods.

Full Log File Available

The complete 1.4MB log file has been downloaded and analyzed. The key failure patterns have been extracted above, but the full logs are available for detailed debugging if needed.

[spbolton]

This issue is being addressed in PR #33227