Unit and End to End (e2e) Testing should be enough – the rest are intangible

I have learned from my years as full time developer that ( those tests, that according to Google’s classification are called medium
), are a life saver. I have also learned from my years as a team leader that these tests are the perfect excuse to deliver tight coupled, AKA 3v1l untestable code
.

If Unit tests are covering all the functionality of your loosely couple software and e2e tests are covering all common scenarios followed by your users, I would name the medium tests “intangible tests”. They are useful as ad-hoc tests that aim at getting a proof of concept (POC) out of the door. However maintaining them, relying on them for application quality and delaying your delivery because of them will be nothing more than paying a big opportunity cost.

Quick Glossary:

  1. Small Tests: “Local Memory” Tests. Hopefully your current Unit tests.
  2. Medium Tests: “Local Host” Tests. Hopefully you don’t maintain them.
  3. Large Tests: “Any Host” Tests. Hopefully your current e2e tests.

The local host tests should not be run as part of your pipeline. They are intangible. I would keep them in the project just for historical reasons, if I would ever keep them.

稿源:Thinking In Software (源链) | 关于 | 阅读提示

本站遵循[CC BY-NC-SA 4.0]。如您有版权、意见投诉等问题,请通过eMail联系我们处理。
酷辣虫 » 综合技术 » Unit and End to End (e2e) Testing should be enough – the rest are intangible

喜欢 (0)or分享给?

专业 x 专注 x 聚合 x 分享 CC BY-NC-SA 4.0

使用声明 | 英豪名录

登录

忘记密码 ?

切换登录

注册