If your team size is larger than say 10-15, consider adding dedicated test results reporting at the same time you are setting up CI/CD too. I'm involved with Te

If your team size is larger than say 10-15, consider adding dedicated test results reporting at the same time you are setting up CI/CD too. I'm involved with Tesults (https://www.tesults.com https://www.tesults.com) and found most teams make do with the reporting built into the CI system thinking it's good enough but it's not at all if you have a large enough team and have a lot of integration/system level tests that need to provide accessible logging, adequate failure reasons and you need to keep track of who's looking into a test fail and do things like keep a handle on recurring fails. If you're working on an open source project (non commercial) then they are currently looking to launch something new that will be free to use for those teams and are accepting emails at the bottom of the front page to talk to interested teams. Appreciation of automation goes up when you have good reporting set up, along with actions that are taken in reaction to failures. If you're going to the trouble of implementing CI then I expect you have at least some expectation of doing fairly regular check-ins, but if it's just a couple of you then of course you're probably fine relying on the built in reporting. With respect to CI you're spoiled for choice now compared to just a 4-5 years ago when these cloud providers like CircleCI and travis did not exist. Jenkins is still the most flexible in my opinion but requires you to be a bit more serious in terms of putting on your build engineer 'hat'.