![Nomad Goods Launches 15% Sitewide Sale for 48 Hours Only [Deal]](https://www.iclarified.com/images/news/96899/96899/96899-640.jpg)
![Apple Watch Series 10 Prototype with Mystery Sensor Surfaces [Images]](https://www.iclarified.com/images/news/96892/96892/96892-640.jpg)
![[The AI Show Episode 142]: ChatGPT’s New Image Generator, Studio Ghibli Craze and Backlash, Gemini 2.5, OpenAI Academy, 4o Updates, Vibe Marketing & xAI Acquires X](https://www.marketingaiinstitute.com/hubfs/ep%20142%20cover.png)
![Is this a suitable approach to architect a flutter app? [closed]](https://i.sstatic.net/4hMHGb1L.png)
![From broke musician to working dev. How college drop-out Ryan Furrer taught himself to code [Podcast #166]](https://cdn.hashnode.com/res/hashnode/image/upload/v1743189826063/2080cde4-6fc0-46fb-b98d-b3d59841e8c4.png?#)
Should release/deployment builds run tests again?
In many configurations of CI/CD pipelines I encounter, things run somewhat like this: compilation and tests are run on a pull request after merging, the build is triggered on the main branch, which runs the compilation and tests again when we want to deploy, we create a tag, which triggers a build that will also compile and test before deploying I sometimes wonder if running the tests in the last build isn't overkill. Sometimes, developers complain that it slows down the process. They argue that the tests have already been run for that commit. Is there anything regarded as best practice here?
In many configurations of CI/CD pipelines I encounter, things run somewhat like this:
- compilation and tests are run on a pull request
- after merging, the build is triggered on the main branch, which runs the compilation and tests again
- when we want to deploy, we create a tag, which triggers a build that will also compile and test before deploying
I sometimes wonder if running the tests in the last build isn't overkill. Sometimes, developers complain that it slows down the process. They argue that the tests have already been run for that commit.
Is there anything regarded as best practice here?
