Yicong-Huang opened a new issue, #5217:
URL: https://github.com/apache/texera/issues/5217

   ### Task Summary
   
   `amber/src/main/scala/org/apache/texera/web/resource/` has ~30 files of 
which ~7 ship with tests. A self-contained cluster of pure-logic helpers — no 
DB, no servlet container, no auth — can be covered in one PR:
   
   - `EmailTemplate.scala` — `userRegistrationNotification` admin / user 
branches, `createRoleChangeTemplate`; subject/content shape and the 
`[deployment]` suffix toggle off `UserSystemConfig.appDomain`.
   - `dashboard/FulltextSearchQueryUtils.scala` — `getFullTextSearchFilter` 
pgroonga / fallback branches and empty-input guards, `getContainsFilter` 
set-based OR, `getDateFilter` open-ended ranges and `ParseException`, 
`getOperatorsFilter` LIKE construction.
   - `dashboard/hub/EntityTables.scala` — `BaseEntityTable / LikeTable / 
CloneTable / ViewCountTable` dispatch maps for `WORKFLOW` and `DATASET` entity 
types.
   - `HealthCheckResource.scala` — single-method status map.
   - `SuccessExecutionResult.scala` — case-class defaults.
   
   Out of scope (heavier mocking, follow-ups):
   
   - `SystemMetadataResource` — needs `OperatorMetadataGenerator` bootstrap
   - `WorkflowWebsocketResource` / `CollaborationResource` — need a 
`javax.websocket.Session` double
   - `UserConfigResource` — DB-backed, follow-up like #5210 / #5213
   - `SyncExecutionResource` / `GmailResource` — large, already have partial 
coverage
   - Dashboard-resource cluster (Workflow / Hub / Project / etc.) — DB-heavy, 
separate bundles
   
   ### Task Type
   
   - [x] Testing / QA


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