How Development Teams Can Benefit From Working With Tests in a CI/CD (TeamCity example)
summary
Live TeamCity demo (Kotlin repo: missingdays/teamcity-tests-demo) shows per-test visibility, durations and slow-test sorting, real-time failure detection while builds run, and automatic flaky detection with history to trace agent or environment causes. It demonstrates assigning investigations across configurations, using service messages to attach screenshots, numbers or artifacts as test metadata, and enforcing quality via coverage gating (fail builds when line coverage drops). Config files are included so the examples are reproducible.
AI-written summary · about
chapters (6)
related talks
34mFrom build to Continuous Delivery in TeamCity
20mContinuous Workflow
45mContinuous Workflow (Team Tools)
34mUsing Test Automation for Continuous Integration, Delivery and Quality
28mUsing CI to Test the Frontend: the TeamCity Example
32mGame DevOps: Elevating Your Unity and Unreal Build Pipelines With TeamCity
01h 29mKeeping Your CI–CD Pipeline as Fast as it Needs to Be
18mThe missing piece of the continuous integration puzzle