Open victoralfaro-dotcms opened 2 weeks ago
QA Notes: Since this is merely for developers usage to test this initiative please run:
# Build dotCMS
./mvnw -DskipTests clean install
Then
# Java E2E tests
./mvnw -pl :dotcms-e2e-java verify -De2e.test.skip=false
and
# Node.js E2E tests
./mvnw -pl :dotcms-e2e-node verify -De2e.test.skip=false
To kill any remaining containers run:
./mvnw -pl :dotcms-e2e -Pdocker-stop -De2e.test.skip=false
E2E testing for both Java and Node.js work perfectly. This is what I can see in my local:
Approved: Tested on trunk_ea7843a, Docker, macOS 14.5, FF v126.0.1
Parent Issue
https://github.com/dotCMS/core/issues/29350
User Story
As a dev-ops/CICD engineer, I want to create a new Maven module project to be included in the main dotCMS root Maven project file. This file should reference any new dependencies from the application BOM file, so changes in the corresponding POM will be required. Additionally, there should be some sort of output indicating a forked process that needs to be executed by a Maven plugin (probably
Failsafe
) at the same phase of integration and Postman tests.Acceptance Criteria
Failsafe
) is configured to execute a forked process during the integration and Postman test phases.dotCMS Version
master
Proposed Objective
Core Features
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
_todefine
Assumptions & Initiation Needs
Quality Assurance Notes & Workarounds
Sub-Tasks & Estimates
Failsafe
) for forked process - 3 hours