Some questions about continuous integration

yzTyzT Member Posts: 365 ■■■□□□□□□□
In your company, who's responsible for the CI system: ops, devs or qa?

Does QA even make sense using CI?


  • Options
    DoubleNNsDoubleNNs Member Posts: 2,015 ■■■■■□□□□□
    I think it makes a ton of sense for QA to do CI. They are often the most experienced members in the org on test cases and know what success looks like. Modern QA also has automation as the backbone of their skills. Great fit, in my opinion.
    Goals for 2018:
    Certs: RHCSA, LFCS: Ubuntu, CNCF CKA, CNCF CKAD | AWS Certified DevOps Engineer, AWS Solutions Architect Pro, AWS Certified Security Specialist, GCP Professional Cloud Architect
    Learn: Terraform, Kubernetes, Prometheus & Golang | Improve: Docker, Python Programming
    To-do | In Progress | Completed
  • Options
    LeBrokeLeBroke Member Posts: 490 ■■■■□□□□□□
    Most places I've seen, DevOps or SRE team sets it up and then QA actually ends up managing the day-to-day of it. Helps that they're not only responsible for creating tests and test automation, but they're also usually responsible for managing releases.

    And yes, it makes perfect sense for QA to use/manage it. CI, after all, is in many ways about test-driven development, so expanding your battery of tests (unit, integration, UI, load, etc) is almost as important as shipping new application features, since the more test automation you have, the less manual testing you have to do, and the less time you need to ship a release.

    For example, at my old place, a QA guy fully automated performance/load testing, to the point where we could pinpoint minor changes in batch processing performance down to individual branches (via feature toggles), after each nightly run. So any time a dev accidentally shipped something that nuked our performance, we could address it pretty much right away, leading to a lot less surprises in production.
Sign In or Register to comment.