Passed Run of Oct 24, 01:31
pytest --flakytest-profile --flakytest-rate 2000.
Where the time goes
Test time by category- Database12.43 s
- Libraries5.14 s
- Migrations2.75 s
- Password hashing2.01 s
- DB schema1.42 s
- Templates1.24 s
- Imports534 ms
- App code311 ms
- Serialization271 ms
- Unsampled208 ms
- pytest150 ms
- Deep copies79 ms
- Test code23 ms
- Factories22 ms
- Waiting22 ms
- Logging6 ms
- Mocking4 ms
- Cache3 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: 26.6s of test time on a 2-CPU machine. With pytest-xdist this could take about 13.3s.
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.2s.
Details
Where:
- apps/api/tests.py:487 ProfileUploadTest.upload · 605 ms
- apps/guides/content.py:112 render · 467 ms
- apps/mcp/tests.py:67 McpTest.post · 460 ms
- ft/tests.py:204 TestAccountSettings.test_change_password · 433 ms
- apps/projects/urls.py:498 project_profile · 397 ms
- apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 305 ms
- apps/orgs/views.py:33 org_shell · 303 ms
- ft/tests.py:160 TestAccountPages.test_signup · 237 ms
- ft/tests.py:199 TestAccountSettings.test_change_password · 218 ms
- apps/projects/urls.py:49 find_project · 214 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/projects/tests.py::ProfilePagePaginationTest::test_slowest_tests_first_then_the_next_page
- apps/projects/tests.py::ProjectPagesTest::test_dashboard_filters
- apps/api/tests.py::TestApiIndex::test_index
- ft/tests.py::TestAccountPages::test_signup
- apps/orgs/tests.py::MembersTest::test_owner_invites_someone_who_signs_up
Disable django-debug-toolbar in tests
django-debug-toolbar is installed in the test settings and costs 8.1s.
Details
Where:
- apps/guides/content.py:112 render · 467 ms
- ft/tests.py:204 TestAccountSettings.test_change_password · 433 ms
- apps/projects/urls.py:498 project_profile · 397 ms
- apps/orgs/views.py:33 org_shell · 303 ms
- apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 279 ms
- ft/tests.py:160 TestAccountPages.test_signup · 237 ms
- ft/tests.py:199 TestAccountSettings.test_change_password · 218 ms
- apps/projects/urls.py:49 find_project · 214 ms
- apps/api/urls.py:72 api_request.<locals>.decorator.<locals>.wrapped_view · 179 ms
- ft/urls.py:151 <module> · 174 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/projects/tests.py::ProfilePagePaginationTest::test_slowest_tests_first_then_the_next_page
- ft/tests.py::TestAccountPages::test_signup
- apps/projects/tests.py::ProjectPagesTest::test_dashboard_filters
- apps/api/tests.py::TestApiIndex::test_index
- apps/guides/tests.py::TestGuidePages::test_every_guide_renders
Make the test database server skip durability work
Tests spend 16.6s (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/environments.py:63 get_or_create_environment · 310 ms
- apps/orgs/views.py:33 org_shell · 300 ms
- apps/projects/models.py:466 Profile.save · 298 ms
- apps/projects/profiles.py:334 write_snapshots · 291 ms
- apps/api/tests.py:76 IngestStartEndpointTest.join_workers · 228 ms
- apps/projects/urls.py:49 find_project · 213 ms
- apps/api/urls.py:72 api_request.<locals>.decorator.<locals>.wrapped_view · 179 ms
- apps/projects/tests.py:954 ProjectPagesTest.setUp · 178 ms
- apps/projects/rollups.py:88 add_perfs · 178 ms
- apps/projects/urls.py:40 can_manage_project · 155 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_ingest_progress_before_start
- apps/projects/tests.py::ProjectPagesTest::test_configure_page
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_progress_end
- apps/api/tests.py::IngestStartEndpointTest::test_results_are_counted_and_the_payload_dropped
- apps/api/tests.py::IngestStartEndpointTest::test_all_test_status_types
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_end_after_progress
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 2.7s 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/0014_backfill_session_counts.py:23 backfill · 5 ms
- apps/projects/migrations/0012_backfill_session_environments.py:30 backfill · 5 ms
- apps/projects/migrations/0022_backfill_organizations.py:69 forwards · 4 ms
- apps/projects/migrations/0016_profile_parts.py:9 move_documents · 4 ms
- apps/projects/migrations/0025_backfill_slugs_and_numbers.py:35 forwards · 4 ms
- apps/projects/migrations/0025_backfill_slugs_and_numbers.py:28 forwards · 3 ms
- apps/projects/migrations/0015_store_compressed_documents_as_is.py:12 external_storage · 3 ms
- apps/projects/migrations/0018_profile_stats_applied.py:9 mark_applied · 3 ms
- apps/projects/migrations/0009_auto_20240218_1217.py:12 create_mute_objects · 1 ms
- apps/projects/migrations/0012_backfill_session_environments.py:24 backfill · 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.8s and collection 303ms on every run, even when you only run one test.
Use a fast password hasher in tests
2.0s (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 · 426 ms
- ft/tests.py:231 TestAccountSettings.test_projects_only_lists_your_own_even_for_superusers · 258 ms
- apps/orgs/tests.py:194 SuperuserTest.test_superusers_can_open_any_project_but_dont_list_them · 241 ms
- apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 226 ms
- ft/tests.py:160 TestAccountPages.test_signup · 220 ms
- ft/tests.py:214 TestAccountSettings.test_change_password · 214 ms
- ft/tests.py:199 TestAccountSettings.test_change_password · 214 ms
- ft/tests.py:176 TestAccountSettings.setUpTestData · 212 ms
- apps/projects/tests.py:139 ProjectEditPage.setUpTestData · 1 ms
- apps/projects/tests.py:407 TestProjectTestPage.setUpTestData · 0.94 ms
Most affected tests:
- ft/tests.py::TestAccountSettings::test_change_password
- ft/tests.py::TestAccountSettings::test_projects_only_lists_your_own_even_for_superusers
- 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::TestAccountPages::test_signup
- apps/projects/tests.py::ProjectEditPage::test_invalid_form
- apps/projects/tests.py::TestProjectTestPage::test_not_logged_in
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_ingest_start_progress_end
- apps/api/tests.py::IngestStartEndpointTest::test_details_are_kept_for_failures_only
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_valid
- 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_results_are_counted_and_the_payload_dropped
- apps/api/tests.py::ProfileUploadLockTest::test_upload_while_a_part_is_being_processed
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_multiple_sessions
Tests open new database connections over and over
Connecting to the database takes 1.0s.
Details
Where:
- apps/api/tests.py:76 IngestStartEndpointTest.join_workers · 184 ms
- apps/api/tests.py:73 IngestStartEndpointTest.setUp · 91 ms
- apps/api/tasks.py:266 warm_reports · 50 ms
- apps/api/urls.py:72 api_request.<locals>.decorator.<locals>.wrapped_view · 44 ms
- apps/api/tests.py:331 IngestStartEndpointTest.test_results_are_counted_and_the_payload_dropped · 29 ms
- apps/api/tests.py:928 ProfileUploadLockTest.setUp · 21 ms
- apps/api/tests.py:257 IngestStartEndpointTest.test_ingest_end_after_progress · 12 ms
- apps/api/tasks.py:237 process_profile · 11 ms
- apps/api/tests.py:212 IngestStartEndpointTest.test_ingest_start_progress_end · 11 ms
- apps/api/tests.py:235 IngestStartEndpointTest.test_ingest_progress_before_start · 11 ms
Most affected tests:
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_progress_end
- 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_all_test_status_types
- apps/api/tests.py::IngestStartEndpointTest::test_ingest_progress_before_start
- apps/api/tests.py::ProfileUploadQueueTest::test_upload_is_processed_by_the_worker
- apps/api/tests.py::IngestStartEndpointTest::test_details_are_kept_for_failures_only
- apps/projects/tests.py::FlakyReportTest::test_report
Create shared test data in setUpTestData instead of setUp
setUp() runs before every test and takes 933ms in total (db 874ms, library 47ms, factories 6ms) 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 · 199 ms
- apps/api/tests.py:73 IngestStartEndpointTest.setUp · 134 ms
- apps/projects/tests.py:143 ProjectEditPage.setUp · 82 ms
- apps/projects/tests.py:101 ProjectsPageTest.setUp · 58 ms
- apps/projects/tests.py:338 ProjectTestsPage.setUp · 58 ms
- ft/tests.py:180 TestAccountSettings.setUp · 57 ms
- apps/projects/tests.py:413 TestProjectTestPage.setUp · 55 ms
- apps/projects/tests.py:1413 MemoryTest.setUp · 48 ms
- apps/projects/tests.py:308 ProjectRunPage.setUp · 40 ms
- apps/projects/tests.py:269 ProjectRunsPage.setUp · 39 ms
Most affected tests:
- apps/projects/tests.py::TestProjectTestPage::test_project_test_page
- apps/projects/tests.py::ProjectEditPage::test_project
- apps/api/tests.py::ProfileUploadLockTest::test_upload_while_a_part_is_being_processed
- apps/projects/tests.py::ProjectEditPage::test_project_submit
- apps/projects/tests.py::ProjectPagesTest::test_runs_page
- apps/projects/tests.py::ProjectsPageTest::test_other_peoples_project
- ft/tests.py::TestAccountSettings::test_email
- apps/projects/tests.py::ProjectCreatePage::test_not_logged_in
Tests
201–253 of 253, slowest first · click a column to sort this pageMemory
The test process peaked at 215 MBSlowest fixtures
Exact setup time across the session| Fixture | Scope | Calls | Total |
|---|---|---|---|
| _django_setup_unittest | class | 54 | 3.03 s |
| django_db_setup | session | 1 | 3.02 s |
| _unittest_setUpClass_fixture_ProjectPagesTest | class | 1 | 287 ms |
| _unittest_setUpClass_fixture_TestAccountSettings | class | 1 | 224 ms |
| _unittest_setUpClass_fixture_ProfilePagePaginationTest | class | 1 | 209 ms |
| _unittest_setUpClass_fixture_McpTest | class | 1 | 183 ms |
| _unittest_setUpClass_fixture_AnalyticsTest | class | 1 | 178 ms |
| _unittest_setUpClass_fixture_RealProfileDocumentTest | class | 1 | 136 ms |
| _unittest_setUpClass_fixture_MemoryTest | class | 1 | 86 ms |
| _unittest_setUpClass_fixture_StorageTest | class | 1 | 80 ms |
| _unittest_setUpClass_fixture_FlakyReportTest | class | 1 | 69 ms |
| _unittest_setUpClass_fixture_LegacyUrlTest | class | 1 | 60 ms |
| _unittest_setUpClass_fixture_UnstorableCharactersTest | class | 1 | 52 ms |
| _unittest_setUpClass_fixture_FlakyReportCacheTest | class | 1 | 50 ms |
| _unittest_setUpClass_fixture_TestProjectTestPage | class | 1 | 22 ms |