- 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.
推薦閱讀
- Docker and Kubernetes for Java Developers
- Spring 5企業級開發實戰
- The Android Game Developer's Handbook
- Amazon S3 Cookbook
- 軟件架構:Python語言實現
- INSTANT Django 1.5 Application Development Starter
- OpenCV 4計算機視覺項目實戰(原書第2版)
- C專家編程
- Advanced UFT 12 for Test Engineers Cookbook
- Distributed Computing in Java 9
- Python全棧開發:基礎入門
- 軟件測試技術
- Clojure編程樂趣
- 零基礎PHP從入門到精通
- 城市信息模型平臺頂層設計與實踐