What you actually install

Each framework with the plugins that bring it closest to Test Junkie's features. pytest alone, without plugins, is 12,606 KB (6 packages, 3.8× the size of Test Junkie); Robot Framework alone is 5,998 KB.

Features, and where they come from

Every feature Test Junkie has built in, and what the other frameworks need for it: built in, a plugin, or not available from any maintained package.

Every package, its size and why it's there

Packages you install yourself come first; the rest are pulled in by them. A package needed by several others is installed, and counted, once.

Test Junkie

pytest

Robot Framework

unittest

pytest: what pip installs behind your back

You name 10 packages. pip installs 28: each one declares what it needs, pip installs those, then what they need, and so on. The 18 packages you never named add up to 16,736 KB, 81% of the install.

pytest 2,937 KB
├─ colorama 166 KB
├─ iniconfig 36 KB
├─ packaging 974 KB
├─ pluggy 135 KB
└─ Pygments 8,358 KB
pytest-xdist 326 KB
├─ execnet 300 KB
└─ pytest already installed above
pytest-rerunfailures 142 KB
├─ packaging already installed above
└─ pytest already installed above
pytest-order 111 KB
└─ pytest already installed above
pytest-randomly 32 KB
└─ pytest already installed above
pytest-html 115 KB
├─ Jinja2 1,147 KB
│  └─ MarkupSafe 56 KB
├─ pytest-metadata 34 KB
│  └─ pytest already installed above
└─ pytest already installed above
pytest-json-report 61 KB
├─ pytest already installed above
└─ pytest-metadata already installed above
pytest-cov 116 KB
├─ coverage 1,436 KB
├─ pluggy already installed above
└─ pytest already installed above
pytest-github-actions-annotate-failures 19 KB
└─ pytest already installed above
pytest-monitor 85 KB
├─ pytest already installed above
├─ requests 468 KB
│  ├─ charset-normalizer 734 KB
│  ├─ idna 506 KB
│  ├─ urllib3 908 KB
│  └─ certifi 248 KB
├─ psutil 816 KB
├─ memory-profiler 204 KB
│  └─ psutil already installed above
└─ wheel 208 KB
   └─ packaging already installed above

How each hidden package got there

Every chain from a package you installed to one you didn't. Two levels deep means it was needed by something that was itself pulled in. pytest-monitor alone brings an HTTP client stack (requests, urllib3, idna, charset-normalizer, certifi) and wheel, because it can upload results to a server. pytest itself brings pygments, the largest package in the whole install, to color tracebacks.

test_junkie 864 KB
├─ psutil 816 KB
├─ appdirs 62 KB
├─ colorama 167 KB
└─ coverage 1,436 KB

robotframework 5,998 KB
robotframework-pabot 540 KB
└─ robotframework already installed above
robotframework-retryfailed 30 KB
└─ robotframework already installed above
coverage 1,436 KB

parameterized 139 KB
unittest-parallel 51 KB
└─ coverage 1,436 KB
html-testRunner 62 KB
└─ Jinja2 1,147 KB
   └─ MarkupSafe 56 KB
unittest-xml-reporting 114 KB
└─ lxml 9,073 KB
coverage already installed above

How it was measured

Environment

A new virtual environment per framework, CPython 3.12.5 on Windows (x64), packages installed with pip install in one command per framework. Versions are the latest on PyPI on October 7, 2026; Test Junkie 0.9a6.

What counts

Every file pip recorded for a package inside site-packages: code, the .pyc files compiled at install, compiled extensions, data files and the package's .dist-info. Not counted: pip itself, and the small launcher programs pip creates for command-line tools, whose size depends on the operating system.

Shared packages

A package several others need (packaging, coverage, jinja2) is installed once and counted once.

Other platforms

Packages with compiled parts (psutil, lxml, markupsafe, charset-normalizer) are smaller or larger on Linux and macOS, and on Linux pytest doesn't install colorama. The totals move by a few percent; the order doesn't change.

Test Junkie's own dependencies

Counted like everyone else's: coverage (1,436 KB) for --code-cov, psutil (816 KB) for resource monitoring, colorama and appdirs. Without them the test_junkie package itself is 864 KB.

Speed comparisons are on the performance benchmark page.