Frun1na opened a new issue, #4763: URL: https://github.com/apache/rocketmq-dashboard/issues/4763
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) and found no similar issue. ### What Happened Several api-layer test fixtures and mock datasets feed values into the test suite that the backend never sends. The suite stays green while asserting against a contract that does not exist, which is exactly how two recent real regressions stayed invisible for weeks (#4732: the consumer page rendered raw filter-mode codes; #4741: protocol tags lost their color — both were covered by tests whose mocks used the old values). Examples (full list in the linked PR): | file | fixture value | backend value | |------|----------------|---------------| | `api/liteTopic.test.ts` | session `status: 'active'`, `ttlStatus: 'active'` | `ACTIVE` / `EXPIRED`; `UNKNOWN / EXPIRED / EXPIRING_SOON / ACTIVE` | | `api/dlq.test.ts`, `mock/dlq.ts` | group `status: 'active' \| 'empty'` | `ACTIVE / EMPTY / UNAVAILABLE` | | `api/producer.test.ts` | `language: 'JAVA'` | `ClientLanguage.name()` → `Java` | | `api/message.test.ts` | `deliveryStatus: 'SUCCESS'` | `success / failed / pending` | | `api/ops.test.ts` | `level: 'critical'` | `error / warning / info` | | `mock/consumers.ts` | `filterMode: 'Tag 过滤' \| 'SQL92 过滤' \| '全量'` | `TAG / SQL / CLASS_FILTER` | ### Expected Behavior Test fixtures and mock datasets use the values the API actually returns, so a contract regression turns the suite red instead of hiding behind stale mocks. ### Steps to Reproduce Inspect the fixtures listed above against the corresponding providers / enums (`RocketMQLiteTopicProvider`, `RocketMQDLQProvider`, `ProducerConnectionService`, `DeliveryStatus`, `AlertLevel`, `SubscriptionFilterModes`). ### Environment - RocketMQ Studio `rocketmq-studio` @ `cd448e17` - `web/src/api/*.test.ts`, `web/src/mock/*.ts` ### Are You Willing to Submit a Pull Request? Yes — #4762 fixes this. -- 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]
