DEV Community

Suraj Shrestha
Suraj Shrestha

Posted on • Edited on

3 2

Do you run Integration Tests during each CI build?

Integration tests are tests that cross boundary. There are many pros and cons of running those every time.

Pros

  • A more complete functionality test

Cons

  • Slow
  • External dependencies not related to the code you are testing
  • Need to create external test environment (e.g. test database, qa account in prod)
  • Network restrictions from CI server in Enterprise environment

So, what do you do?

Top comments (1)

Collapse
 
syuraj profile image
Suraj Shrestha

Last time I was running some Integration tests that calls Google Translate api.
The tests were failing and Azure Pipelines was rerunning those tests for some reason.
Unfortunately, Google Translate isn't free. So, it ended up costing me $400 for some stupid integration tests that I ignored :(.

Billboard image

The Next Generation Developer Platform

Coherence is the first Platform-as-a-Service you can control. Unlike "black-box" platforms that are opinionated about the infra you can deploy, Coherence is powered by CNC, the open-source IaC framework, which offers limitless customization.

Learn more

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay