mengw15 opened a new issue, #7226:
URL: https://github.com/apache/texera/issues/7226

   ### Task Summary
   
   `WorkflowExecutionsResource` 
(`amber/src/main/scala/org/apache/texera/web/resource/dashboard/user/workflow/WorkflowExecutionsResource.scala`,
 codecov ~64%) has a `MockTexeraDB` spec, but the execution-metadata jOOQ 
endpoints are largely untested. Extend it. The result/log-URI and size methods 
go through `DocumentFactory` / replay — scope those out.
   
   ### Behavior to add
   
   In the existing `MockTexeraDB`-backed spec, seed a workflow + executions via 
DAOs and cover the DB endpoints:
   
   - `getWorkflowExecutions` / `retrieveExecutionsOfWorkflow` / 
`retrieveLatestExecutionEntry` / `getLatestExecutionID` — list executions and 
the latest for a workflow (empty and populated).
   - `insertOperatorExecutions` — persist operator executions; assert the rows.
   - `setExecutionAreBookmarked` / `updateWorkflowExecutionsName` — the 
bookmark flag / name change round-trips.
   - `groupDeleteExecutionsOfWorkflow` — delete a set of executions and assert 
removal.
   - `retrieveInteractionHistory` / `retrieveWorkflowRuntimeStatistics` 
(DB-metadata portion) — the returned records for seeded data.
   
   Out of scope (storage / replay): `getResultUris*` / `getConsoleMessagesUri*` 
/ `getRuntimeStatsUri*` / `removeAllExecutionFiles` / `exportResultTo*` / 
`update*Size` / `getWorkflowResultDownloadability` (they use `DocumentFactory` 
/ `ReplayLogRecord`).
   
   ### Task Type
   - [ ] Refactor / Cleanup
   - [ ] DevOps / Deployment / CI
   - [x] Testing / QA
   - [ ] Documentation
   - [ ] Performance
   - [ ] Other
   


-- 
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