Enhance E2E Test Flexibility with Multi-Mode Execution and Debugging

[victoralfaro-dotcms]

Parent Issue

Add flexibility to E2E tests execution

User Story

As a dev-ops engineer, I want to add flexibility to the recently created E2E tests to run in different modes so that the tests can be more adaptable and efficient in different environments and workflows.

Acceptance Criteria

• Ability to run a specific test file for both Java and Node.js.
• Debug mode for Node.js tests is added.
• HTML output is generated when CI is detected to be false.
• Test results open immediately when tests finish running outside of CI.
• All options are added in the just file.

dotCMS Version

master

Proposed Objective

Integrations

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

• Slack discussion #devops
• E2E test documentation link to doc

Assumptions & Initiation Needs

• Access to the just file for modifications.
• Node.js and Java test frameworks are properly configured.
• CI system can detect non-CI runs.

Quality Assurance Notes & Workarounds

• Ensure that running tests in all modes (specific file, folder, tag) works consistently across environments.
• Verify that debug mode logs appropriately for troubleshooting.
• Ensure HTML output opens correctly when not in CI.

Sub-Tasks

• Implement specific test file run for Java/Node.js
• Implement folder/tag-specific Node.js test execution
• Add debug mode for Node.js tests
• Implement HTML output and auto-open behavior
• Update just file with all new options
• Testing & QA

[github-actions]

PRs:

• #30373: adding useful E2E commands to justfile and to E2E documentation #31010
• #30373: adding useful E2E commands to justfile and to E2E documentation #31058

[victoralfaro-dotcms]

QA Notes

Please follow the instructions https://github.com/dotCMS/core/tree/main/e2e/dotcms-e2e-node specifically for:

• When running specific test file or test folders
• When debuguing specific test file interact with debugger
• Verify that HTML results are displayed in browser (you will need to Crtl-C to kill the instance serving the results)