Github Actions: Software testing

CI/CD Testing

File	Role
app.py	Business logic
test_app.py	Automated control
pytest	Testing engine
ci.yml	Control procedure
GitHub Actions	Control execution system

Continuous Integration

Continuous Integration (CI) is the automation pipeline (for example GitHub Actions or Jenkins), and automated tests (such as pytest) are the checks that validate the code.

name: Auditor CI/CD Pipeline
on:
  push:
    branches:
      - main
jobs:
  build-test-deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout Code
        uses: actions/checkout@v4
      - name: Set up Python
        uses: actions/setup-python@v5
        with:
          python-version: '3.11'
      - name: Install Dependencies
        run: |
          python -m pip install --upgrade pip
          pip install -r requirements.txt
      - name: Run Tests
        run: |
          pytest
      # CD demonstration (simulation)
      - name: Deploy (Simulation)
        run: |
          echo "Deploying application..."
          echo "Deployment successful!"

Dimension	QA Testing Workshop	DevOps Engineering Workshop	CI/CD & Governance Workshop
Primary Objective	Ensure software quality through testing and defect detection	Build and operate automated delivery systems	Understand automation controls, governance, and evidence in software delivery
Focus	Test strategy, manual & automated testing, defect lifecycle	Infrastructure, deployment, pipelines, automation	CI/CD concepts, control points, audit evidence, risk
Tools Used	Testing tools (e.g. Selenium, manual test cases) and frameworks like pytest	Infrastructure tools (Docker, Kubernetes), pipelines, cloud platforms	Automation pipelines like GitHub Actions or Jenkins
Use Case	Validate software meets requirements and quality standards	Deliver software faster and operate systems reliably	Govern automation, understand controls, and audit software delivery
Strength	Deep quality assurance and defect prevention	Operational efficiency and delivery speed	Governance mindset and understanding of automation risks
Weakness	Does not cover deployment or infrastructure	Requires technical depth in infrastructure	Less technical depth in coding/deployment
Target Audience	QA engineers, testers, quality managers	DevOps engineers, platform engineers	Auditors, governance professionals, managers
Outcome	Better software quality	Faster and reliable delivery	Better understanding of controls and automation evidence
Example Activity	Write test cases and execute them	Build pipelines and deploy systems	Analyze pipelines and map control points
Tools Knowledge Required	Moderate (testing frameworks)	High (infrastructure & automation)	Low to moderate (conceptual)

Keyword: Testing, CI/CD