Achieving CI Excellence with Quality Engineering
•
2 likes•79 views
Quality Engineering roles continue to evolve and will be entirely different in the future. At Gannett | USA Today Network, the change has started by blurring the lines between Test Automation and DevOps daily tasks with Quality Engineering owning continuous integration (CI), defining CI best practices, building the CI pipeline, and being the quality gatekeeper of product releases. - Setting expectations for CI- - CI ownership as a community activity, not an individual one - Defining a continuous testing strategy - Designing repeatable and disposable CI architecture - Setting CI standards - Quality Engineering roles and responsibilities
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Achieving CI Excellence with Quality Engineering
Similar to Achieving CI Excellence with Quality Engineering (20)
Recently uploaded
Recently uploaded (20)
Achieving CI Excellence with Quality Engineering
- 1. Achieving CI Excellence with Quality Engineering http://unsplash.com
- 2. Director/Quality Engineering Greg Sypolt 110NewsMarkets @gregsypolt in/gregsypolt Blogger Speaker Conference greg@qualityelement.com </QUALITYELEMENT.COM>
- 3. Agenda http://unsplash.com Setting Expectations for CI CI Ownership as a Community Activity, Not an Individual One Defining a Continuous Testing Strategy and Path to Production Designing Repeatable and Disposable CI Architecture Setting CI Standards Quality Engineering Roles and Responsibilities
- 5. Evolution of Continuous Integration Self-Hosted Manual On-Premise Self-Service Model
- 6. The Vision Shifting LEFT with DevOps and Automated Testing Code Build Test Deploy MonitorPlanCollaborate building quality into every stage Repeat It takes a COMMUNITY Dev | Pre-Prod | Prod Discovery Execute Release Review How We Test Things
- 7. Expectations for Continuous Integration Adapt Build Confidence Share Adapt Set Clear Goals
- 9. CI Ownership as a Community Product EngineeringPlatform Engineering Quality Engineering </> </> Build Unit Integration Pull Request Code √ √ √ Tests √ √ √ √ √ √ Others Stage Acceptance Others √ √ √ √ √ √ Tests Production Others √ √ √ Synthetics √ √ √ Tests Build better software by improving speed, efficiency, and collaboration Teamwork Vision Goals StrategyInnovation Success MeasureElevate Ideas Culture of Quality Best Practices Collect Requirements Coach and Mentor Create Pipeline Code Maintain Infrastructure Containerization Monitoring Results Identifying Quality Gaps
- 10. Defining A Single Path To Production http://unsplash.com
- 11. Pre-Commit Commit Acceptance Capacity Exploratory Production Stages Infrastructure Any plan that defers testing is BROKEN … Defining a Single Path to Production
- 12. Define A Continuous Testing Strategy http://unsplash.com
- 13. Define a Continuous Testing Strategy Test Continuously Instant Feedback on Quality Reduce Risk Build Confidence Faster Release Cycles Infrastructure Unit Module/Component API Integration User Acceptance Visual Performance Stress Security Scalability Developer Pre-Production Production Commit Creation Pull Request Merged Pull Request Deployment Disposable Infrastructure Automate Everything New Relic Monitoring Blue/Green Deployments Canary Trigger Points Environments Quality PlaybookShift Left DevOps
- 14. Design Continuous Integration Architecture http://unsplash.com
- 15. Monitoring App Deployment Managed CI Architecture Code Source Control CI Workers CI Workers CI Workers CI Workers CI Server Persistent Volume Snapshots EBS Artifact Storage ETC Platform Eng APIs & Tools Sauce Labs Applitools AWS Device Farm QASymphony Artifact Storage
- 16. Defined Continuous Integration Standards http://unsplash.com
- 17. Continuous Integration Standards Multiple Teams Artifact RepoJenkinsfile Notifications Manage SecretsWebhooksMonitoring More … Kubernetes PV Snapshots EBS Containers Shared Libraries Insights
- 18. Pipeline as Code Agent Stages Stage Parallel Basic Pipeline Terms Restricting Builds Retrieving Repositories Docker Image Build (Compiling Code) Running Tests Deploy to Environment Reporting Test Details Push Build Artifacts Notification Scripting Pipeline Code In general, most Pipeline scripts look more or less like this… Jenkinsfile Commit Acceptance Capacity Exploratory Production
- 20. Quality Specialist Software Development Engineer in Test (SDET) Quality Engineering Roles and Responsibilities Continuous Integration Operations Test Infrastructure Voice of Quality and Collect Requirements Coach and Mentor Evangelize How We Test Things Defining the Testing Strategy Identifying Quality Gaps Manual Testing Exploratory Testing Post Mortem’s Monitoring Testing Results Create Pipeline Code for Tests Containerization Create Insights Dashboards Best Practices Documentation Continuous Integration Defining the Continuous Testing Manage CI Images Manage CI Infrastructure Monitoring CI Infrastructure