Download to read offline
Uploaded byRTTS
Building your CI/CD Test Automation Strategy with GitHub Actions
Building Your CI/CD Test Automation Strategy with GitHub Actions Speakers: - Bill Hayduk, CEO, RTTS - Jan Chris Tacbianan, QA Manager, Senior Solutions, Architect, RTTS ---------------------------------------------------------------------------------------------------------------- Shipping code faster is a key goal of CI/CD, but speed without quality leads to problems. The solution is a powerful automated testing strategy built directly into your development workflow. GitHub Actions is more than just a CI/CD runner; it can provide a complete ecosystem for ensuring quality at every stage of development. Session Overview ------------------------------------------- In this 30-minute webinar, we will show you how to leverage GitHub Actions to create a comprehensive testing pipeline that goes beyond simple unit tests. - CI/CD with GitHub Actions: A quick overview on GitHub Actions and its capabilities - Full-Stack Testing Possibilities: Learn what testing is possible to automate, including API (e.g., Postman/Newman), Data, and UI (e.g., Playwright). - Strategic Pipeline Design: How to start building your strategy to provide rapid feedback to developers and full validation before deployment. Throughout the session, we will apply these strategies in a hands-on demonstration with a sample application, providing you with a clear blueprint for success. For more information, go to www.rttsweb.com
More Related Content
Similar to Building your CI/CD Test Automation Strategy with GitHub Actions
Building your CI/CD Test Automation Strategy with GitHub Actions
- 1. Building Your CI/CD TestAutomation Strategy with GitHub Actions Bill Hayduk Founder & CEO Jan Tacbianan Senior Solutions Architect QA Group Manager
- 2. The premier pure-play automatedQA & testing experts providing innovative Test Automation solutions to 700+ companies since 1996
- 3. RTTS is theinnovative QA & testing firm that has specialized in Test Automation since 1996 RTTS FACTS Founded: 1996 (29th anniversary) Location: New York City (HQ) Customer profile: • North America • Fortune 500 & midsize • 700+ customers Software Supported • QuerySurge • Microsoft Azure DevOps • Selenium • JMeter • Postman • Provar • Appium • CitraTest • SmartBear • Jira • GitHub • UFT • OWASP • many others
- 4. Agenda ❑ CI/CD andGitHub Actions ❑ Full-Stack Testing Capabilities ❑ Strategic Pipeline Design ❑ Demo
- 5. What is CI/CD? ❑ContinuousIntegration (CI) is the practice of frequently merging all developer code into a central repository ❑ Continuous Delivery (CD) extends CI by automatically deploying all code changes to a testing and/or production-ready environment after the build stage. ❑ Continuous Deployment is a fully automated process that releases every change that passes all stages of your pipeline directly to customers. ❑ CI/CD stands for Continuous Integration and Continuous Delivery / Continuous Deployment.
- 6. What is GitHubActions? ❑ GitHub Actions is a CI/CD platform within the GitHub designed to automate build, test, and deployment pipelines. A Sample PR Workflow
- 7. What is GitHubActions? ❑ Event Driven – GitHub Action workflows are triggered by different events (push, PRs, schedules, manual, etc.) ❑ Defined as Code – Written in YAML files and are version controlled. ❑ Flexible – Workflows run on GitHub hosted “runners” or bring your own self-hosted runners. Use readily available “Actions” or customize your own. ❑ Reusable – Actions can be reused across different workflows.
- 8. Full-Stack Testing Capabilities ❑A comprehensive testing strategy can help test the entire tech stack: ❑ Code-Level Testing ❑ Service and API Testing ❑ Back-end and Database Testing ❑ Web UI Testing ❑ Native Mobile UI Testing ❑ Accessibility Testing ❑ Security Testing
- 9. Strategic Pipeline Designwith Test Automation ❑ Shift Left Testing ❑ Tiered Feedback Loop ❑ Automate Where Possible Requirements Design Develop Test Deploy Maintain Traditional Testing Shift Left Testing
- 10. Shift Left Testing ❑Test Early and Test Often ❑ "Shifting left" means integrating testing into the earliest stages of the development cycle. This philosophy is key to a successful strategy. ❑ Run tests automatically on every code change, not just before a release ❑ By catching bugs early, you dramatically reduce the cost and effort required to fix them. Requirements Design Develop Test Deploy Maintain Traditional Testing Shift Left Testing
- 11. Tiered Feedback Loop ❑The Test Pyramid ❑ Each level of the pyramid can potentially be automated. Example: ❑ Code Level and Unit Tests ❑ On every commit or every push ❑ Integration and Contract Tests ❑ On every pull request ❑ End-to-end Tests ❑ Scheduled/Nightly
- 12. Automate Where Possible ❑There are many components that are overlooked when automation is considered: ❑ Infrastructure changes can be tested ❑ Networking and access rules can be tested ❑ Security patches and updates can have regression tests automated