> But during development, did you ever run nightly tests / all tests?
I strongly recommend people I work with to use my script that modifies circle ci, which ops us into running all tests; I tend to see people use this as it makes CI faster, but has this by product as well. So yes, all tests should be run before merge. There are examples of Jenkins only tests that are not run, but again this is due to existing limitations with Jenkins. > On Jan 30, 2023, at 3:33 PM, Henrik Ingo <henrik.i...@datastax.com> wrote: > > On Tue, Jan 31, 2023 at 1:28 AM David Capwell <dcapw...@apple.com > <mailto:dcapw...@apple.com>> wrote: >> If the CI coverage isn't 100%, then we should just identify the gaps, and >> focus on that while preparing to merge > > It has 100% coverage that is done normally for trunk merges; which is a > pre-commit CI run in Circle OR Jenkins. > > > Sure. And thanks. > > But during development, did you ever run nightly tests / all tests? I > wouldn't want the night after merging to trunk to be the first time those are > run. > > henrik > -- > > Henrik Ingo > c. +358 40 569 7354 > w. www.datastax.com <http://www.datastax.com/> > <https://www.facebook.com/datastax> <https://twitter.com/datastax> > <https://www.linkedin.com/company/datastax/> <https://github.com/datastax/>
