mattcasters opened a new pull request, #7506:
URL: https://github.com/apache/hop/pull/7506

   ## Summary
   
   Speeds up Hop integration tests by running each project suite in a **single 
hop-run JVM** instead of restarting the JVM for every `main-*.hwf` (issue 
#7494). On this machine, `transforms` went from ~13 minutes to ~4 minutes.
   
   ### Changes
   
   - **Surefire Report Output** transform 
(`plugins/transforms/surefirereport`): accumulates test result rows and writes 
Maven Surefire 3.0 XML (name, duration, pass/fail, logs) for Jenkins junit 
reporting.
   - **Shared runner**: `integration-tests/scripts/run-project-tests.hpl` + 
`run-workflow.hwf` — GetFileNames → WorkflowExecutor → Surefire Report Output 
(continue after individual failures; fail suite after report is written).
   - **`run-tests.sh`**: default path uses the shared runner; set 
`HOP_IT_PER_TEST_JVM=true` for classic one-JVM-per-test isolation.
   - **WorkflowExecutor**: execution-result stream keeps input fields (e.g. 
`filename`) so test names reach Surefire.
   - **0059 Get Files Rows Count IT**: pin the original four `.txt` files 
instead of `*.txt` (extra `text-file-input-rownum.txt` had broken expected 
104/4 counts).
   
   Parallel test execution is left for a follow-up; Hop variables are local, so 
it should be viable later.
   
   ## Test plan
   
   - [x] Unit tests for Surefire Report Output + WorkflowExecutor meta 
serialization
   - [x] Manual: single-JVM transforms suite produces `surefile_transforms.xml` 
and passes
   - [ ] Jenkins daily IT (`Hop-integration-tests`) still publishes junit from 
`integration-tests/**/surefire-reports/*.xml`
   - [ ] Spot-check another large suite (e.g. `mdi`) if needed
   - [ ] Isolation fallback: `HOP_IT_PER_TEST_JVM=true` still works
   
   ## Reviewer note
   
   @hansva — especially interested in your take on the Jenkins/surefire side, 
since you built the original IT suite wiring. Parallelism can wait; this PR is 
the single-JVM + reporting foundation.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to