Test channel callbacks with MockPulse

Purpose and runtime

MockPulse is an optional channel callback simulator in this repository, not the production support service. It combines a React frontend with Tauri / Rust desktop capabilities. A web preview does not provide every native execution feature.

cd mock-pulse
yarn install
yarn tauri:dev

Install Rust and the Tauri prerequisites for your operating system as described in the MockPulse README ↗. yarn dev starts a web preview only.

Build a reproducible case

1. Run DuDu Server, Console and Desk. Create an organization, employees, groups and the target channel account.
2. Prepare event materials and scenarios for the target adapter, matching the test account’s signature, encryption and callback settings. Arbitrary JSON is not a universal channel request.
3. Organize scenarios into a plan and execute it. Use run records and server responses to locate failures.
4. Check incoming messages, ordering, history and current access scope in Desk. Sending validation separately requires real credentials and a usable official API.

Validation boundaries

Controlled local callbacks can validate protocol processing and the support workflow. They do not establish real-platform authorization, public callback reachability or production review approval. Simulating incoming messages does not automatically simulate official outbound APIs. Record real-platform acceptance separately.

Next steps

Follow the WeChat, Telegram or WhatsApp guide for platform preparation. The MockPulse source README ↗ defines current implementation and runtime limits.