Answers: <p>Continuous Testing is a <a href="https://en.wikipedia.org/wiki/Continuous_integration" rel="nofollow noreferrer">side effect</a> of Continuous Integration. CI's main purpose is to integrate your development efforts into a production-ready state as often as possible. The production-readiness is granted via continuously testing the recently integrated code. Continuous Integration does not work properly without Continuous Testing, but you could continuously test without making your development code production ready all the time. In my experience the CT term is not really in use anymore.</p>
  
Answers: CC BY-SA 4.0
Answers: 2022-06-03T12:24:31.323Z
Answers: 2022-06-03T12:24:31.323Z
Answers: YoshiMbele
Body: <p>What is the difference between testing in the context of Continuous Integration pipeline vs testing in context of Continuous Testing pipeline? The definition of testing is a bit blurred to me in the context of CT pipeline.</p>
  <p>An example, I understand testing in CI where a Unit Test is executed on a Pull Request - personally I'd defined it as a Continuous Testing since I continuously test incoming code however, this practice is known as CI. Then, what is CT then? Am I only one confusing CI for CT?</p>
  
Tags: <continuous-integration>
Title: What is difference between testing in context of CI and CT pipelines?
UserDisplayName: Lukasz Dynowski
ThreadText: # What is difference between testing in context of CI and CT pipelines?
  
  (Asked by: username_0 on 2022-06-03)
  
  What is the difference between testing in the context of Continuous Integration pipeline vs testing in context of Continuous Testing pipeline? The definition of testing is a bit blurred to me in the context of CT pipeline.
  
  An example, I understand testing in CI where a Unit Test is executed on a Pull Request - personally I'd defined it as a Continuous Testing since I continuously test incoming code however, this practice is known as CI. Then, what is CT then? Am I only one confusing CI for CT?
  
  **Tags:** continuous-integration
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2022-06-03. Score: 2
  
  Continuous Testing is a [side effect](https://en.wikipedia.org/wiki/Continuous_integration) of Continuous Integration. CI's main purpose is to integrate your development efforts into a production-ready state as often as possible. The production-readiness is granted via continuously testing the recently integrated code. Continuous Integration does not work properly without Continuous Testing, but you could continuously test without making your development code production ready all the time. In my experience the CT term is not really in use anymore.
  
  
  ---
  
  