Project 3: Complete Framework with Reports and CI

Selenium 20 min min read Updated: Nov 16, 2026 Advanced
Project 3: Complete Framework with Reports and CI
Advanced Topic 3 of 4

Goal

Turn everything you learned into one repository you can show in interviews. The application under test can be saucedemo.com or any public practice site.

Checklist of Features

FeatureLesson used
Driver factory: Chrome, Firefox, headless, remote GridBrowsers, Framework structure, Grid
Config per environment and secrets from .envConfig lesson
Page objects with a BasePage and componentsPOM lessons
Explicit waits onlyWaits
Data-driven tests from JSON/CSVparametrize
Markers: smoke, regressionMarkers
Allure report with steps and screenshots on failureReports
Parallel execution with xdistParallel lesson
Docker compose with Selenium GridDocker lesson
GitHub Actions: smoke on push, regression nightlyCI lesson
README with setup and badgeGit lesson

Repository Layout

text qa-automation-framework/ .github/workflows/ smoke.yml nightly.yml config/config.json pages/ (base_page.py, login_page.py, inventory_page.py, ...) tests/ smoke/ regression/ test_data/users.json utils/ (driver_factory.py, config.py, data.py, logger.py) conftest.py pytest.ini docker-compose.yml Dockerfile requirements.txt .env.example README.md

Step by Step Plan

  1. Create the repository and virtual environment, commit the empty structure
  2. Write driver_factory.py, config loader and the root conftest.py
  3. Create BasePage and the first two page objects with tests; make them pass
  4. Add JSON test data and parametrized tests
  5. Add markers and a pytest.ini with --strict-markers
  6. Add Allure: steps in page methods and screenshot attachment on failure
  7. Add pytest -n auto and fix any test that is not independent
  8. Add docker-compose.yml for the Grid and run with --remote
  9. Add the GitHub Actions workflows and fix CI differences
  10. Write the README: purpose, tech, how to run, how to view reports, project structure, sample report screenshot

Allure Steps in a Page Object

python import allure class LoginPage(BasePage): @allure.step("Log in as {user}") def login(self, user, password): self.type(self.USERNAME, user) self.type(self.PASSWORD, password) self.click(self.LOGIN_BTN)

GitHub Actions: Smoke and Nightly

yaml # .github/workflows/nightly.yml name: Nightly Regression on: schedule: - cron: "0 21 * * *" workflow_dispatch: jobs: regression: runs-on: ubuntu-latest services: selenium: image: selenium/standalone-chrome:latest ports: ["4444:4444"] options: --shm-size=2g steps: - uses: actions/checkout@v4 - uses: actions/setup-python@v5 with: { python-version: "3.12", cache: pip } - run: pip install -r requirements.txt - run: pytest -m regression -n 4 --remote=http://localhost:4444 --alluredir=allure-results - uses: actions/upload-artifact@v4 if: always() with: name: allure-results path: allure-results

Make It Stand Out

  • A screenshot of the Allure report in the README
  • A short Architecture section with the folder diagram
  • A Known limitations section (honest and professional)
  • Meaningful commits and a few merged pull requests
  • A 2 minute screen recording of a run

How to Present in an Interview

  • Explain why you chose each tool (pytest for fixtures, POM for maintenance, Docker for repeatable browsers)
  • Be ready to explain one flaky test you fixed and how
  • Describe how you would add a new test or a new page in 5 minutes

Conclusion

A complete framework shows employers that you can design, build and maintain automation, not only write scripts. Keep the repository tidy and documented.

Quick Summary: Driver factory + config + POM + data + Allure + xdist + Docker + CI + README.

Get Newsletter

Subscibe to our newsletter and we will notify you about the newest updates on Edugators