Tirsvad-Udemy-100-days-of-code/048-scrapping-wiki
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Page: Docker Testing
Pages
Docker Testing da Docker Testing ms Docker Testing Home da Home ms Home Lecture Steps da Lecture Steps ms Lecture Steps Setup and Run da Setup and Run ms Setup and Run
Clone
1
Docker Testing
Tirsvad edited this page 2026-10-28 09:30:36 +01:00
Table of Contents

Docker Testing

🌐 English · Dansk · Bahasa Malaysia

Why Docker

A script that drives a browser opens windows and uses the mouse and keyboard focus of the machine it runs on. To keep the developer's desktop free, the end to end run and the screenshots run in a Docker container with headless Chromium. Unit tests need no browser and run on the host.

Build and run

docker build -t scraping-wiki-e2e .
docker run --rm -v "$(pwd)/results:/results" scraping-wiki-e2e

The container reports through files in results/:

File Content
e2e.log The combined output of the test and the screenshot capture
exit-code.txt 0 when everything passed
screenshots/ One PNG for each of the seven lecture steps

What runs

  1. tests/e2e/test_interaction_e2e.py runs python -m scraping_wiki.interaction --headless and checks that one number is printed and that it is at least one million (the article count, not the active editors).
  2. tests/e2e/capture_screenshots.py renders the code of steps 1 to 3 as an editor page, takes real screenshots of the Wikipedia main page for steps 4, 5 and 7, and shows the real output in step 6.

Keeping secrets out

The .dockerignore file keeps .env, .venv and .git out of the image. The project never reads or imports the .env file.

Scraping Wiki

Related

Languages