mengw15 opened a new pull request, #7370:
URL: https://github.com/apache/texera/pull/7370

   ### What changes were proposed in this PR?
   
   Extends `user-workflow.component.spec.ts` to render the template branches the
   existing class-focused tests never reached, taking 
`user-workflow.component.html`
   from ~53% to 100% (104/104; the class was already at 221/221). 11 new tests 
under
   a `template rendering` block:
   
   - **toolbar** — the Create button, the sort-button's `sortMethodChange`, and 
the
     view-type List/Card toggle.
   - **multi-select actions** (rendered only once an entry is checked) — Batch
     Select, Download-as-ZIP, Duplicate, and the Delete popconfirm.
   - **project actions** — the add/remove-from-project buttons that appear when 
a
     `pid` is set.
   - **outputs** — the rendered `texera-search-results` outputs (deleted / 
duplicated
     / refresh / notifyWorkflow) and the `#workflowCardTpl` card in card view 
with
     its card-item outputs (deleted / duplicated / refresh / checkboxChanged).
   
   Interactions go through the DOM (`By.css` + `triggerEventHandler`); the 
backing
   services are the existing stubs. No production code was changed.
   
   ### Any related issues, documentation, discussions?
   
   Closes #7362.
   
   ### How was this PR tested?
   
   `ng test --watch=false --include 
src/app/dashboard/component/user/user-workflow/user-workflow.component.spec.ts`
   — 69 passed (58 existing + 11 new), run 3x for determinism. Coverage 
(`--coverage`)
   confirms `user-workflow.component.html` at 104/104 and the class at 221/221. 
The
   failure path was verified by breaking an assertion (red, non-zero exit); 
eslint and
   prettier are clean.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Opus 4.8 [1M context])
   


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