Automate Admin — ENG-4938 + ENG-5306 + ENG-5307 QA Report

TC1 — Steps & Result

1. Navigated to /categories via sidebar (Categories tag icon, bottom of nav).
2. Verified table loaded with columns: Category Name, Assigned Workflows, Created On, Edit/Delete actions.
3. Confirmed pagination showed "Showing 1 to 29 of 29 results".
4. Verified table is sortable and rows show workflow count numbers.

Result: Table rendered correctly with all expected columns and data.

TC2 — Steps & Result

1. Clicked "+ New" button — "Create a new category" modal opened.
2. Entered name "Sense HR Essentials" → clicked Save → row appeared in table (30 results).
3. Attempted to create duplicate "Sense HR Essentials" → error message shown: duplicate rejected.
4. Attempted lowercase duplicate "sense hr essentials" → same error, confirming case-insensitive duplicate check.

Result: Category creation, duplicate detection (case-insensitive), and table update all work correctly.

TC3 — Steps & Result

1. Clicked the pencil icon on "Sense HR Essentials" row → "Edit category" modal opened pre-populated with existing name.
2. Changed name to "Sense HR Advanced" → clicked Save.
3. Row updated to "Sense HR Advanced" in the table.
4. Attempted edit to an existing name → duplicate error correctly shown.

Result: Edit modal opens with current name, rename persists, duplicate names blocked.

Note: The Edit modal only exposes the Category Name field — no workflow assignment is available from Edit. Workflow count is read-only in the table.

TC4 — Steps & Result

1. Clicked trash icon on "Sense HR Advanced" (0 assigned workflows) → Confirmation dialog appeared: "Are you sure you want to delete this category?" with No / Yes.
2. Clicked No → dialog dismissed, "Sense HR Advanced" remained in table.
3. Clicked trash icon again → same confirmation dialog appeared.
4. Clicked Yes → "Sense HR Advanced" removed, table updated to 29 results.

Result: Delete + confirmation flow works. Cancel (No) preserves the row. Confirm (Yes) removes it.

Bug noted: Confirmation dialog appears for categories with 0 assigned workflows. Spec says only show when category has assigned workflows. See Bugs section.

TC1 — Steps & Result

1. Loaded /categories — sidebar was in collapsed state (icon-only, ~50px wide).
2. Clicked the hamburger menu icon (top-left) → sidebar expanded, all navigation labels appeared (Organisations, Workflows, Installations, Auto-Install Workflows, Published Workflows, Service Connections, All Instances, Categories).
3. Clicked hamburger again → sidebar collapsed back to icon-only.

Result: Expand/collapse toggle works correctly. All navigation labels visible when expanded.

TC2 — Steps & Result

1. Expanded state: Clicked "Organisations" text link → /organisations loaded with active nav highlight.
2. Collapsed state: Navigated using icon-only refs for Installations → /installations loaded correctly.
3. Confirmed active route highlighting updates appropriately in both states.

Result: All tested navigation items work in both expanded and collapsed sidebar states. Icon-only navigation is functional when labels are hidden.

TC1 — Steps & Result

1. Navigated to the Configuration schema tab (Drafts → Configuration schema sub-tab).
2. Observed the "Add new:" row at the bottom of the parameter table.
3. Default type (Text): Default Value field = plain <input> (standard text input).
4. Changed Type dropdown to Multi-Select.
5. After selecting Multi-Select: Default Value field changed to <p-multiselect> — a chip-capable multi-select control.

DOM verification:

Result: When parameter type is changed to Multi-Select, the Default Value field correctly switches to a p-multiselect chip control, distinct from the plain text input used for Text parameters.

TC2 — Steps & Result

1. On the same Configuration schema page, changed Type dropdown to Select.
2. Observed Default Value field: rendered as P-SELECT — a single-value dropdown selector, NOT a chip-based control.
3. Confirmed no p-multiselect, p-chips, or p-autocomplete-input-multiple classes present in the Default Value column for Select type.

Result: When parameter type is "Select" (single select), the Default Value field remains a standard single-value control (p-select dropdown) with no chip UI. The multi-select chip behaviour is correctly scoped to "Multi-Select" type only.