flakytest.dev anze3db fedidevs
Docs Sign In
All environments · last 30 days

Tests

Slowest Most memory Failing & flaky

301 tests, most memory first

Peak above the memory the test's process had when it started
Test Needs Max Kept after Runs
stats/tests.py::TestStats::test_store_daily_stats_with_accounts 0 KB 0 KB 0 KB 4
Measured in the process that ran the test, from its setup to its teardown. Exact on Linux; on macOS and Windows a test's peak is only known when it raised its process's peak. Databases, browsers and subprocesses aren't included. How memory is measured