YouZan Low-Code Platform BOS: Testing Strategy and Implementation Guide
The guide explains YouZan’s low‑code BOS platform, its component‑based architecture, and a multi‑level testing methodology—including automated component, product, and workflow tests, traffic replay, performance checks, and a robust fallback mechanism—to ensure seamless migration and reliable operation of digitized business processes.
This article introduces YouZan's low-code platform BOS (Business Operating System) and its testing methodology. BOS is a commercial operating system that digitizes business elements (advertising, sales, products, logistics, marketing, etc.) and provides building tools for integrating these digital elements to construct various business workflows.
1. BOS Overview: BOS enables enterprises to digitally register business elements as "components" that can be assembled through no-code orchestration, replacing traditional coding methods. The platform includes data standards, component access standards, application orchestration models, rule engines, data connectors, component extension standards, automated testing/OPS, product authorization, product templates, and developer certification systems.
2. Test Case Design: BOS structures business requirements into workflows composed of products, which consist of activity tasks, further composed of components. Test cases are designed at three levels: component-level, product-level, and workflow-level to achieve precise and comprehensive testing coverage.
3. Test Automation Strategy: The automation strategy follows the BOS development process: first structure requirements and create component-level automated cases; these serve as entry criteria for development self-testing and QA testing; before pre-release, execute full component-level automation cases; during pre-release testing, execute full pre-release automation cases plus traffic replay.
4. Traffic Replay Testing: For read interfaces, use online collection with offline replay. For write interfaces (e.g., order creation), separate the read-only portion and compare return values between old and BOS workflows on pre-release environment. A future plan involves using shadow links with shadow tables for comparison.
5. Performance Testing: Single-machine pressure testing compares performance metrics between old and new workflows at the same QPS to ensure no performance degradation after BOS transformation.
6. Fallback Strategy: A detailed fallback mechanism handles BOS platform exceptions during traffic switching, automatically falling back to old workflows with monitoring alerts to prevent impact on production business.
Youzan Coder
Official Youzan tech channel, delivering technical insights and occasional daily updates from the Youzan tech team.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.