What Should a WeChat Mini Program Livestream POC Test? A Script for Live, Replay, Chat, Products and Login
A livestream proof of concept should run under the company’s own Mini Program AppID with a test channel, real member states and a product destination.
A livestream proof of concept should run under the company’s own Mini Program AppID with a test channel, real member states and a product destination. “Video plays” is only one test result. POLYV WebView, native SDK and uni-app mp-weixin integrations need a recorded script covering live and replay viewing, chat, interactions, products, login and small-window behavior.
Run the POC with the company’s own AppID and product page, preserving reproducible iOS and Android evidence.
01 / Freeze the POC environment
Record the AppID, service category, player permissions, experience-build number, SDK or component version, channel ID, iOS and Android models and WeChat versions. Prepare channels that are live, not yet live and completed with replay. Use accounts that are logged out, entitled and restricted by viewing conditions. Capture channel configuration before testing so a later change is not mistaken for an SDK defect.
02 / Run six core cases
First, enter a live room from the real activity page and record start time and first-frame result. Second, open a completed channel and verify replay controls and exit. Third, use two accounts to send and receive chat messages. Fourth, trigger one configured interaction. Fifth, click a product, open the company’s product detail, place a test order and return. Sixth, expire or switch a login session and verify access conditions without identity leakage. Each case needs inputs, steps, expected result, actual result and evidence.
03 / Add device and failure cases
On iOS and Android, change networks, navigate to a product page, return, share a card and enter through that card. Test duplicate clicks and interrupted sessions. Treat small-window playback as a separate case: a native route checks its current player; a WebView live route checks its intermediary page and the return to H5. Use actual devices rather than treating developer-tool simulation as a pass.
04 / Define a decision-ready result
Business acceptance means the correct member and product destination are used and the test order retains campaign attribution. Technical acceptance means live and replay work on target devices, chat and interactions reflect channel settings, and errors can be identified and recovered. Mark launch blockers, experience issues and enhancements separately, with owners and retest builds. The POC conclusion should state which integration route is recommended and what remains open.
05 / Six executable POC cases
Before testing, record AppID, channel ID, component and WeChat versions, plus target phones. Agree any numerical first-frame or recovery thresholds in advance.
| Case | Preconditions and action | Pass criterion | Evidence |
|---|---|---|---|
| P01 Live | Enter an active channel from the business page | Correct stream, channel and campaign source | Recording, start time, channel state |
| P02 Replay | Enter after replay becomes available | Correct replay, seek and exit behavior | Recording, replay ID, settings |
| P03 Chat | Two test accounts exchange messages | Messages map to the right accounts | Two-device recording and timestamps |
| P04 Interaction | Trigger one configured interaction | Viewer sees the expected state | Admin setting and device capture |
| P05 Product | Click a test product and place an order | Product, member, campaign and order correlate | Navigation recording and test order |
| P06 Login | Expire or change the member session | Access rules apply without account leakage | Account state and recording |
A commerce POC should treat P01, P05 and P06 as blockers. Education projects can prioritize course access and replay accordingly. Record the responsible system and retest build for every failure.
Frequently Asked Questions
Should a POC include checkout? If livestream commerce is the goal, a test order is needed to verify the product and attribution path.
Is developer-tool preview enough? No. Playback, sharing, navigation and small-window behavior require target iOS and Android devices.
How should POC results be recorded? Save conditions, steps, expected and actual behavior, device, recording and owner for every case.
Further Reading
Continue with A WeChat Mini Program Livestream Launch Checklist: Shares, Product Routes, Analytics and Return Paths and How to Test Mini Program Small-Window Playback on Native and WebView Routes Across iOS and Android. For the overall integration choice, see the WeChat Mini Program SDK guide. The Chinese edition covers the same task for local teams.
About POLYV
POLYV Mini Program viewing capabilities include playback, chat and interactions. A POC should turn the official scope into repeatable cases under the company’s own AppID and channel.