- 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.
推薦閱讀
- Microsoft Exchange Server PowerShell Cookbook(Third Edition)
- R語言游戲數(shù)據(jù)分析與挖掘
- Practical DevOps
- Hands-On Microservices with Kotlin
- 程序員修煉之道:通向務(wù)實(shí)的最高境界(第2版)
- Vue.js 2 Web Development Projects
- C語言程序設(shè)計(jì)簡(jiǎn)明教程:Qt實(shí)戰(zhàn)
- Everyday Data Structures
- Python自然語言理解:自然語言理解系統(tǒng)開發(fā)與應(yīng)用實(shí)戰(zhàn)
- Java Web開發(fā)實(shí)例大全(基礎(chǔ)卷) (軟件工程師開發(fā)大系)
- SignalR:Real-time Application Development(Second Edition)
- Mastering Apache Camel
- Android編程權(quán)威指南(第4版)
- Python編程:從入門到實(shí)踐(第2版)
- GitHub Essentials