- 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.
推薦閱讀
- UML和模式應用(原書第3版)
- Java范例大全
- Getting Started with PowerShell
- Practical DevOps
- Mastering OpenCV 4
- Unity Shader入門精要
- Visual C#.NET程序設計
- Selenium Testing Tools Cookbook(Second Edition)
- 軟件測試實用教程
- Create React App 2 Quick Start Guide
- Solr Cookbook(Third Edition)
- Learning Material Design
- Canvas Cookbook
- Hands-On Full Stack Development with Spring Boot 2.0 and React
- 軟件測試技術