unbridled-41 commented on PR #3984:
URL: 
https://github.com/apache/rocketmq-dashboard/pull/3984#issuecomment-5556765050

   ## Verification evidence
   
   - **CI**: this branch head `51553be5` triggers the upstream `CI` workflow, 
which reports `startup_failure` (workflow never starts — repository-level 
failure, not a job failure): 0 check runs. Recent runs on the base branch fail 
the same way, so no CI signal is available for any PR in this repository; local 
verification below substitutes for it.
   - **Red-light output (before implementation)**: `npx vitest run 
src/stores/aiChatHistoryStore.test.ts src/pages/ai/__tests__/AiPage.test.tsx` → 
`Tests 4 failed | 28 passed (32)`: two store tests failed with `TypeError: 
searchAiChatConversations is not a function`, and the two drawer tests failed 
because no element matched the search-input placeholder `搜索对话记录`.
   - **Module tests (after implementation)**: same two files → `Tests 32 passed 
(32)` (13 store + 19 page), including all pre-existing coverage.
   - **Full suite + baseline comparison**: web `npx vitest run 
--testTimeout=60000` → 926 tests (922 pristine + 4 new), 2 failures — 
`AclPage.test.tsx` and `ConsumerPage.test.tsx`, the known load-flaky files 
untouched by this PR (both files re-run in isolation: 50/50 passed). Zero new 
failures. Backend is not touched; the backend suite is unaffected.
   - **Build**: `npm run build` → `✓ built in 9.77s`; `tsc -b` clean (after 
fixing widened string-literal types in the new test data); `eslint` on the five 
touched files clean.
   - **Diff self-check**: 5 files, +178/−8 — one pure store helper, one search 
input, an entry-mapping that unifies row labels, two i18n keys, tests only 
otherwise. The no-query drawer path renders the same rows as before; no 
unrelated edits.


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