Skip to main content
added suggestion feedback
Source Link

Small teams, if the codebase is small as well, can get away without CI, since their test suite takes so little time to run (just 3-10 minutes, probably).

The real strengths of CI come in when either:

  • you have a complex build to automate
  • you have 20+ minutes of tests to run
  • you publicly display your red-green test scroll by the company water-cooler.

Small teams, if the codebase is small as well, can get away without CI, since their test suite takes so little time to run (just 3-10 minutes, probably).

The real strengths of CI come in when:

  • you have a complex build to automate
  • you have 20+ minutes of tests to run
  • you publicly display your red-green test scroll by the company water-cooler.

Small teams, if the codebase is small as well, can get away without CI, since their test suite takes so little time to run (just 3-10 minutes, probably).

The real strengths of CI come in when either:

  • you have a complex build to automate
  • you have 20+ minutes of tests to run
  • you publicly display your red-green test scroll by the company water-cooler.
Source Link

Small teams, if the codebase is small as well, can get away without CI, since their test suite takes so little time to run (just 3-10 minutes, probably).

The real strengths of CI come in when:

  • you have a complex build to automate
  • you have 20+ minutes of tests to run
  • you publicly display your red-green test scroll by the company water-cooler.