QA in DevOps: Transformation thru Automation via Jenkins
summary
Jenkins becomes the orchestration hub: integrate Git/SVN, trigger builds after every commit, run unit tests, static analysis (FindBugs/PMD) and code‑coverage tools, then run smoke tests to validate environments before heavy GUI regression. Use infrastructure as code (Chef/Puppet/Ansible, Vagrant/Docker) to spin clean VMs, automate test data creation/cleanup, and run small environment‑health checks hourly. Treat initial static analysis as a baseline to avoid paralysis, parallelize and pare regression suites, and consolidate results into a single dashboard for fast go/no‑go decisions.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:39Agenda
- 1:02About me
- 1:32DevOps Key of New Jersey
- 2:00Process Automation
- 3:08DevOps
- 4:50Identifying bottlenecks
- 5:30Automation tests
- 5:54Agile
- 6:18Change
- 6:40Challenges
- 6:53Version Management
- 8:19Build Automation
- 8:39Continuous Integration
- 9:32Continuous Integration Jenkins
- 10:28Unit Testing
- 11:03Testing Pyramid
- 12:56Static Analysis
- 13:06Static Analysis Tools
- 15:38Environment
- 18:09Regression
- 21:18Environment Configuration Deployment
- 22:32Testing Results
- 27:26Target State
- 29:26Conclusion
related talks
35mUsing the DevOps Pipeline to Generate Continuous, Valuable Insights
27mExploring a DevOps Transformation Like a Tester
52mCreating a QA/DEV Collaborative Testing Strategy
31mQA and DevOps: A Journey of Growth, Mistakes, and Learning
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
06mDoes QA have a place in DevOps? Heck yeah!
42mJenkins: Enabling Agility and Efficiency
44mQA in a Pipeline Based Organization