- Continuous Integration,Delivery,and Deployment
- Sander Rossel
- 131字
- 2021-07-02 15:42:09
Incremental testing
With incremental testing, you test components as soon as they are available and you create stubs or drivers (some sort of placeholder) for components that are not yet available. There are two approaches here:
- Top-down testing: Using top-down testing would mean I would've checked whether the external service could make a call to the internal service and, if the internal service was not available yet, create a stub that pretends to be the internal service.
- Bottom-up testing: Bottom-up is testing the other way around, so I'd start testing the internal service and create a driver that mimics the external service.
Incremental testing has the advantage that you can start defining tests early before all the components are complete. After that, it becomes a matter of filling in the gaps.
推薦閱讀
- Visual Studio 2012 Cookbook
- Java高并發核心編程(卷2):多線程、鎖、JMM、JUC、高并發設計模式
- Mastering Objectoriented Python
- Apache Hive Essentials
- Vue.js 3.0源碼解析(微課視頻版)
- C語言程序設計
- Learning SQLite for iOS
- Python金融數據分析
- PHP+MySQL網站開發項目式教程
- UVM實戰
- Mastering Android Game Development
- RealSenseTM互動開發實戰
- Learning AngularJS for .NET Developers
- 深入理解BootLoader
- 零基礎學HTML+CSS第2版