Passed Run of Nov 11, 00:11
pytest --flakytest-profile --flakytest-rate 2000.
Where the time goes
Test time by category- Database12.85 s
- Libraries4.81 s
- Migrations2.95 s
- Password hashing2.11 s
- DB schema1.46 s
- Templates1.20 s
- Imports619 ms
- Unsampled450 ms
- Deep copies340 ms
- App code325 ms
- Serialization245 ms
- pytest227 ms
- Test code39 ms
- Factories19 ms
- Waiting16 ms
- Mocking4 ms
- Cache2 ms
- Logging2 ms
Session timeline
Fix next
Ranked by the time each fix saves per runRun tests in parallel on all 2 CPUs
Tests run one at a time: 27.7s of test time on a 2-CPU machine. With pytest-xdist this could take about 13.8s.
Details
Tests must not share state: files in fixed paths, ports, a shared database without per-worker names, or module globals. Run with -p randomly first to shake out order dependencies.
Use plain static file storage in tests
Static file storage/manifest handling costs 12.0s.
Details
Where:
- apps/mcp/tests.py:67 McpTest.post · 542 ms
- apps/api/tests.py:487 ProfileUploadTest.upload · 524 ms
- apps/guides/content.py:112 render · 479 ms
- ft/tests.py:204 TestAccountSettings.test_change_password · 464 ms
- apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 327 ms
- ft/tests.py:160 TestAccountPages.test_signup · 288 ms
- apps/projects/urls.py:498 project_profile · 234 ms
- ft/tests.py:199 TestAccountSettings.test_change_password · 226 ms
- apps/projects/tests.py:320 ProjectRunPage.test_other_peoples_project · 183 ms
- apps/projects/urls.py:40 can_manage_project · 175 ms
Most affected tests:
- apps/api/tests.py::ProfileUploadTest::test_missing_parts_mark_the_profile_incomplete
- ft/tests.py::TestAccountSettings::test_change_password
- apps/orgs/tests.py::SignupTest::test_signing_up_creates_an_organization
- apps/api/tests.py::TestApiIndex::test_index
- ft/tests.py::TestAccountPages::test_signup
- apps/projects/tests.py::ProjectPagesTest::test_dashboard_filters
- apps/projects/tests.py::ProjectRunPage::test_other_peoples_project
- apps/orgs/tests.py::AccessTest::test_others_dont
Disable django-debug-toolbar in tests
django-debug-toolbar is installed in the test settings and costs 8.3s.
Details
Where:
- apps/guides/content.py:112 render · 479 ms
- ft/tests.py:204 TestAccountSettings.test_change_password · 464 ms
- apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 318 ms
- ft/tests.py:160 TestAccountPages.test_signup · 288 ms
- apps/projects/urls.py:498 project_profile · 234 ms
- ft/tests.py:199 TestAccountSettings.test_change_password · 226 ms
- apps/projects/urls.py:40 can_manage_project · 175 ms
- apps/projects/urls.py:8 <module> · 174 ms
- apps/projects/urls.py:49 find_project · 170 ms
- ft/urls.py:45 index · 160 ms
Most affected tests:
- apps/api/tests.py::ProfileUploadTest::test_missing_parts_mark_the_profile_incomplete
- ft/tests.py::TestAccountSettings::test_change_password
- apps/orgs/tests.py::SignupTest::test_signing_up_creates_an_organization
- ft/tests.py::TestAccountPages::test_signup
- apps/projects/tests.py::ProjectPagesTest::test_dashboard_filters
- apps/api/tests.py::TestApiIndex::test_index
- apps/projects/tests.py::SeedDemoCommandTest::test_seed_demo
- apps/projects/tests.py::ProjectPagesTest::test_duplicate_tests_are_flagged
Make the test database server skip durability work
Tests spend 17.3s (62%) in the database. Test databases don't need to survive a crash, so the server can skip flushing to disk.
Details
Only affects crash safety of the throwaway test server; query behaviour is identical.
Where:
- apps/projects/models.py:466 Profile.save · 351 ms
- apps/projects/tests.py:954 ProjectPagesTest.setUp · 251 ms
- apps/api/tests.py:76 IngestStartEndpointTest.join_workers · 247 ms
- apps/projects/environments.py:63 get_or_create_environment · 233 ms
- apps/projects/profiles.py:352 write_snapshots · 232 ms
- apps/projects/urls.py:40 can_manage_project · 175 ms
- apps/projects/urls.py:49 find_project · 170 ms
- apps/projects/models.py:35 next_number · 165 ms
- apps/projects/profiles.py:497 write_perfs · 157 ms
- apps/projects/models.py:18 get_or_create_numbered · 149 ms
Most affected tests:
- apps/api/tests.py::TestApiIndex::test_index
- apps/projects/tests.py::SeedDemoCommandTest::test_seed_demo
- apps/api/tests.py::IngestStartEndpointTest::test_all_test_status_types
- apps/api/tests.py::IngestStartEndpointTest::test_results_are_counted_and_the_payload_dropped
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_end_after_progress
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_progress_before_start
- apps/projects/tests.py::ProjectPagesTest::test_configure_page
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_progress_end
Repeated queries (N+1) in the code under test
27 tests run the same query 10+ times, e.g. 180x in test_seed_demo. N+1 queries slow the tests and production alike.
Details
This changes application code, so it speeds up production too; the tests stay as they are.
- 180x in test_seed_demo: SELECT "projects_test"."id", "projects_test"."name", "projects_test"."project_id", "projects_test"."slug", "projects_test"."date_last_run", "projects_test"."date_first_seen", "projects_test"."first_commit_id", "projects_test"."muted" FROM "projects_test" WHERE ("projects_test"."name" = %s AND "proj…
- 22x in test_dashboard_filters: SELECT "projects_environment"."id", "projects_environment"."project_id", "projects_environment"."name", "projects_environment"."kind", "projects_environment"."provider", "projects_environment"."details", "projects_environment"."date_first_seen", "projects_environment"."date_last_seen" FROM "project…
- 21x in test_configure_page: SELECT "projects_profile"."id", "projects_profile"."project_id", "projects_profile"."number", "projects_profile"."environment_id", "projects_profile"."session_id", "projects_profile"."run_id", "projects_profile"."commit_id", "projects_profile"."ingest_id", "projects_profile"."external_id", "project…
- 20x in test_index: SELECT "django_content_type"."model" AS "model" FROM "django_content_type" WHERE "django_content_type"."app_label" = %s
- 20x in test_daily_stats_count_a_profile_once_every_part_is_in: SELECT "projects_profilepart"."id", "projects_profilepart"."profile_id", "projects_profilepart"."index", "projects_profilepart"."count", "projects_profilepart"."checksum", "projects_profilepart"."status", "projects_profilepart"."error", "projects_profilepart"."tests_count", "projects_profilepart"."…
Most affected tests:
- apps/projects/tests.py::SeedDemoCommandTest::test_seed_demo
- apps/projects/tests.py::ProjectPagesTest::test_dashboard_filters
- apps/projects/tests.py::ProjectPagesTest::test_configure_page
- apps/api/tests.py::TestApiIndex::test_index
- apps/api/tests.py::ProfileUploadTest::test_daily_stats_count_a_profile_once_every_part_is_in
- apps/api/tests.py::IngestStartEndpointTest::test_all_test_status_types
- apps/api/tests.py::IngestStartEndpointTest::test_details_are_kept_for_failures_only
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_end_after_progress
Stop re-running migrations on every test run
Migrations take 3.0s per run, before the first test can start.
Details
CI should still build the database from scratch (no --reuse-db) so broken migrations are caught.
Where:
- apps/projects/migrations/0025_backfill_slugs_and_numbers.py:24 forwards · 4 ms
- apps/projects/migrations/0004_project_created_by_project_date_created_and_more.py:12 add_created_by_to_project · 3 ms
- apps/projects/migrations/0014_backfill_session_counts.py:23 backfill · 3 ms
- apps/projects/migrations/0022_backfill_organizations.py:48 forwards · 3 ms
- apps/projects/migrations/0025_backfill_slugs_and_numbers.py:28 forwards · 3 ms
- apps/projects/migrations/0025_backfill_slugs_and_numbers.py:35 forwards · 3 ms
- apps/projects/migrations/0009_auto_20240218_1217.py:12 create_mute_objects · 1 ms
- apps/projects/migrations/0012_backfill_session_environments.py:30 backfill · 1 ms
- apps/projects/migrations/0018_profile_stats_applied.py:9 mark_applied · 1 ms
- apps/projects/migrations/0022_backfill_organizations.py:27 forwards · 1 ms
Most affected tests:
- apps/api/tests.py::TestApiIndex::test_index
pytest takes a long time before the first test runs
Startup takes 5.4s and collection 305ms on every run, even when you only run one test.
Use a fast password hasher in tests
2.1s (8% of test time) is spent hashing passwords. Slow hashing protects real passwords; in tests it only burns CPU.
Details
Only change the hasher in test settings. Tests that assert on a specific hash format need updating.
Where:
- ft/tests.py:204 TestAccountSettings.test_change_password · 458 ms
- ft/tests.py:160 TestAccountPages.test_signup · 277 ms
- apps/orgs/tests.py:194 SuperuserTest.test_superusers_can_open_any_project_but_dont_list_them · 248 ms
- apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 245 ms
- ft/tests.py:231 TestAccountSettings.test_projects_only_lists_your_own_even_for_superusers · 242 ms
- ft/tests.py:199 TestAccountSettings.test_change_password · 224 ms
- ft/tests.py:213 TestAccountSettings.test_change_password · 215 ms
- ft/tests.py:176 TestAccountSettings.setUpTestData · 205 ms
- apps/projects/tests.py:332 ProjectTestsPage.setUpTestData · 0.94 ms
- apps/projects/tests.py:399 LegacyUrlTest.test_private_projects_stay_private · 0.83 ms
Most affected tests:
- ft/tests.py::TestAccountSettings::test_change_password
- ft/tests.py::TestAccountPages::test_signup
- apps/orgs/tests.py::SuperuserTest::test_superusers_can_open_any_project_but_dont_list_them
- apps/orgs/tests.py::SignupTest::test_signing_up_creates_an_organization
- ft/tests.py::TestAccountSettings::test_projects_only_lists_your_own_even_for_superusers
- apps/projects/tests.py::ProjectTestsPage::test_not_logged_in
- apps/projects/tests.py::LegacyUrlTest::test_private_projects_stay_private
Use TestCase instead of TransactionTestCase
1.2s goes to flushing every table after tests in 11 TransactionTestCase / transaction=True / live_server tests.
Details
Tests that rely on commit behaviour, multiple connections or a live server still need a transactional test case.
Most affected tests:
- apps/api/tests.py::IngestStartEndpointTest::test_results_are_counted_and_the_payload_dropped
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_multiple_sessions
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_progress_end
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_with_git
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_end_after_progress
- apps/api/tests.py::IngestStartEndpointTest::test_all_test_status_types
- apps/api/tests.py::ProfileUploadQueueTest::test_upload_is_processed_by_the_worker
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_progress_before_start
Tests open new database connections over and over
Connecting to the database takes 1.2s.
Details
Where:
- apps/api/tests.py:76 IngestStartEndpointTest.join_workers · 214 ms
- apps/api/tests.py:73 IngestStartEndpointTest.setUp · 96 ms
- apps/api/tasks.py:266 warm_reports · 65 ms
- apps/api/tasks.py:237 process_profile · 55 ms
- apps/api/urls.py:72 api_request.<locals>.decorator.<locals>.wrapped_view · 54 ms
- apps/api/tests.py:287 IngestStartEndpointTest.test_all_test_status_types · 25 ms
- apps/api/tests.py:331 IngestStartEndpointTest.test_results_are_counted_and_the_payload_dropped · 12 ms
- apps/api/tests.py:975 ProfileUploadQueueTest.setUp · 12 ms
- apps/api/tests.py:235 IngestStartEndpointTest.test_ingest_progress_before_start · 11 ms
- apps/api/tests.py:928 ProfileUploadLockTest.setUp · 11 ms
Most affected tests:
- apps/api/tests.py::IngestStartEndpointTest::test_all_test_status_types
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_progress_before_start
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_end_after_progress
- apps/api/tests.py::ProfileUploadQueueTest::test_upload_is_processed_by_the_worker
- apps/api/tests.py::IngestStartEndpointTest::test_results_are_counted_and_the_payload_dropped
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_progress_end
- apps/api/tests.py::IngestStartEndpointTest::test_details_are_kept_for_failures_only
- apps/projects/tests.py::AnalyticsTest::test_category_breakdown
Create shared test data in setUpTestData instead of setUp
setUp() runs before every test and takes 988ms in total (db 921ms, library 55ms, factories 8ms) in 14 classes: SettingsTest (3 tests), ProjectsPageTest (5 tests), ProjectEditPage (6 tests), ProjectDeletePage (4 tests).
Details
Since Django 3.2 attributes assigned in setUpTestData are deep-copied per test, so in-memory changes don't leak between tests. Keep objects a test modifies in the database (or re-fetches) as before.
Where:
- apps/projects/tests.py:954 ProjectPagesTest.setUp · 266 ms
- apps/api/tests.py:73 IngestStartEndpointTest.setUp · 149 ms
- apps/projects/tests.py:188 ProjectDeletePage.setUp · 83 ms
- apps/projects/tests.py:219 ProjectCreatePage.setUp · 81 ms
- apps/projects/tests.py:101 ProjectsPageTest.setUp · 68 ms
- apps/projects/tests.py:143 ProjectEditPage.setUp · 65 ms
- apps/projects/tests.py:413 TestProjectTestPage.setUp · 49 ms
- apps/projects/tests.py:1429 MemoryTest.setUp · 41 ms
- apps/projects/tests.py:269 ProjectRunsPage.setUp · 38 ms
- ft/tests.py:180 TestAccountSettings.setUp · 29 ms
Most affected tests:
- apps/projects/tests.py::ProjectDeletePage::test_project
- apps/projects/tests.py::ProjectPagesTest::test_htmx_refresh_run_row
- apps/projects/tests.py::ProjectCreatePage::test_invalid_form
- apps/projects/tests.py::ProjectCreatePage::test_not_logged_in
- apps/projects/tests.py::ProjectDeletePage::test_other_peoples_project
- apps/projects/tests.py::ProjectsPageTest::test_not_logged_in
- apps/projects/tests.py::ProjectPagesTest::test_tests_page
- apps/projects/tests.py::ProjectPagesTest::test_projects_page
Tests
1–200 of 254, slowest first · click a column to sort this pageMemory
The test process peaked at 214 MBSlowest fixtures
Exact setup time across the session| Fixture | Scope | Calls | Total |
|---|---|---|---|
| _django_setup_unittest | class | 54 | 3.25 s |
| django_db_setup | session | 1 | 3.24 s |
| _unittest_setUpClass_fixture_ProjectPagesTest | class | 1 | 287 ms |
| _unittest_setUpClass_fixture_TestAccountSettings | class | 1 | 220 ms |
| _unittest_setUpClass_fixture_ProfilePagePaginationTest | class | 1 | 216 ms |
| _unittest_setUpClass_fixture_AnalyticsTest | class | 1 | 200 ms |
| _unittest_setUpClass_fixture_McpTest | class | 1 | 187 ms |
| _unittest_setUpClass_fixture_RealProfileDocumentTest | class | 1 | 147 ms |
| _unittest_setUpClass_fixture_MemoryTest | class | 1 | 88 ms |
| _unittest_setUpClass_fixture_StorageTest | class | 1 | 82 ms |
| _unittest_setUpClass_fixture_FlakyReportTest | class | 1 | 69 ms |
| _unittest_setUpClass_fixture_LegacyUrlTest | class | 1 | 66 ms |
| _unittest_setUpClass_fixture_UnstorableCharactersTest | class | 1 | 57 ms |
| _unittest_setUpClass_fixture_FlakyReportCacheTest | class | 1 | 53 ms |
| _unittest_setUpClass_fixture_IngestEnvironmentTest | class | 1 | 22 ms |