Project 3: Complete Framework with Reports and CI
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
| Feature | Lesson used |
|---|---|
| Driver factory: Chrome, Firefox, headless, remote Grid | Browsers, Framework structure, Grid |
Config per environment and secrets from .env | Config lesson |
Page objects with a BasePage and components | POM lessons |
| Explicit waits only | Waits |
| Data-driven tests from JSON/CSV | parametrize |
| Markers: smoke, regression | Markers |
| Allure report with steps and screenshots on failure | Reports |
| Parallel execution with xdist | Parallel lesson |
| Docker compose with Selenium Grid | Docker lesson |
| GitHub Actions: smoke on push, regression nightly | CI lesson |
| README with setup and badge | Git 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
- Create the repository and virtual environment, commit the empty structure
- Write
driver_factory.py, config loader and the rootconftest.py - Create
BasePageand the first two page objects with tests; make them pass - Add JSON test data and parametrized tests
- Add markers and a
pytest.iniwith--strict-markers - Add Allure: steps in page methods and screenshot attachment on failure
- Add
pytest -n autoand fix any test that is not independent - Add
docker-compose.ymlfor the Grid and run with--remote - Add the GitHub Actions workflows and fix CI differences
- 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.

