- Continuous Integration,Delivery,and Deployment
- Sander Rossel
- 177字
- 2021-07-02 15:42:09
Big bang testing
There are two approaches to integration testing: big bang testing and incremental testing. With big bang testing, you simply wait until all the components of a system are ready and then start testing. In the case of my service, that meant developing and installing everything, then posting some requests and checking whether the external service could call the internal service, and whether the internal service could access the database and the queue and, not unimportant, give feedback to the external service. Furthermore, of course, I had to test whether the queue triggered the processing service and whether the processing service processed the message correctly too.
In reality, the processing also used the database; it put new messages on the queue and sent emails in case of errors. Additionally, all the components had to access the hard drive for logging to a file (and do not assume the filesystem is always available; the first time on production I actually ran into an Unauthorized Exception and nothing was logged). So that means even more integration testing.
- Functional Python Programming
- Learning Real-time Processing with Spark Streaming
- Java Web開發之道
- 編寫高質量代碼:改善Python程序的91個建議
- 概率成形編碼調制技術理論及應用
- ADI DSP應用技術集錦
- H5頁面設計:Mugeda版(微課版)
- AppInventor實踐教程:Android智能應用開發前傳
- Scala編程(第5版)
- JavaScript+jQuery網頁特效設計任務驅動教程
- Vue.js光速入門及企業項目開發實戰
- MyBatis 3源碼深度解析
- Learning Concurrency in Python
- 深入理解Kafka:核心設計與實踐原理
- 和孩子一起學編程:用Scratch玩Minecraft我的世界