Profiles / #12

Passed Run of Nov 7, 23:53

CI github-actions:test · e141198 main dirty · pass/fail report

short_tests 5 tests finished faster than one sample (1ms), so they have timings but no breakdown. That's expected for tests this fast.

Wall time

32.70 s

1 worker

Test time

27.20 s

sum of test durations

Tests

253

253 passed

Profiler

tachyon

1000 Hz · 22,876 samples · Python 3.15.2 · flakytest 2026.0b1

Peak memory

178 MB

test process

Where the time goes

Test time by category

Session timeline

Tests

26.20 s

Startup

4.83 s

Collection

392 ms

Between tests

659 ms

Session teardown

435 ms

Test phases

Setup 5.58 s Call 21.48 s Teardown 135 ms

Fix next

Ranked by the time each fix saves per run

Run tests in parallel on all 2 CPUs

Tests run one at a time: 27.2s of test time on a 2-CPU machine. With pytest-xdist this could take about 13.6s.

High Parallelism

13.60 s per run

Fix: pip install pytest-xdist, then run pytest -n auto (add it to addopts, or only in CI). pytest-django creates a separate test database per worker automatically. Read the guide

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.

Documentation

Use plain static file storage in tests

Static file storage/manifest handling costs 12.7s.

High App code

12.71 s per run

Fix: In test settings use STORAGES["staticfiles"] = {"BACKEND": "django.contrib.staticfiles.storage.StaticFilesStorage"} so templates don't need a manifest. Read the guide

Details

Where:

apps/api/tests.py:487 ProfileUploadTest.upload · 704 ms
apps/mcp/tests.py:67 McpTest.post · 559 ms
ft/tests.py:204 TestAccountSettings.test_change_password · 479 ms
apps/guides/content.py:112 render · 455 ms
apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 313 ms
apps/api/tests.py:98 IngestStartEndpointTest.ingest_start · 312 ms
ft/tests.py:160 TestAccountPages.test_signup · 252 ms
ft/tests.py:199 TestAccountSettings.test_change_password · 252 ms
apps/projects/urls.py:498 project_profile · 188 ms
apps/orgs/views.py:33 org_shell · 180 ms

Most affected tests:

ft/tests.py::TestAccountSettings::test_change_password
apps/api/tests.py::ProfileUploadTest::test_missing_parts_mark_the_profile_incomplete
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::IngestStartEndpointTest::test_ingest_end_after_progress
apps/api/tests.py::TestApiIndex::test_index
apps/projects/tests.py::ProjectRunPage::test_project_with_runs_no_tests

Disable django-debug-toolbar in tests

django-debug-toolbar is installed in the test settings and costs 7.8s.

High App code

7.80 s per run

Fix: Only add debug_toolbar to INSTALLED_APPS and MIDDLEWARE when not testing (e.g. `if DEBUG and not TESTING:`). Read the guide

Details

Where:

ft/tests.py:204 TestAccountSettings.test_change_password · 479 ms
apps/guides/content.py:112 render · 455 ms
apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 302 ms
ft/tests.py:160 TestAccountPages.test_signup · 252 ms
ft/tests.py:199 TestAccountSettings.test_change_password · 252 ms
apps/projects/urls.py:498 project_profile · 188 ms
apps/orgs/views.py:33 org_shell · 180 ms
apps/projects/models.py:18 get_or_create_numbered · 163 ms
apps/projects/urls.py:49 find_project · 158 ms
apps/api/urls.py:59 touch_token · 152 ms

Most affected tests:

ft/tests.py::TestAccountSettings::test_change_password
apps/api/tests.py::ProfileUploadTest::test_missing_parts_mark_the_profile_incomplete
apps/orgs/tests.py::SignupTest::test_signing_up_creates_an_organization
apps/projects/tests.py::ProjectPagesTest::test_dashboard_filters
ft/tests.py::TestAccountPages::test_signup
apps/api/tests.py::TestApiIndex::test_index
apps/projects/tests.py::ProfilePagePaginationTest::test_slowest_tests_first_then_the_next_page
apps/guides/tests.py::TestGuidePages::test_every_guide_renders

Documentation

Make the test database server skip durability work

Tests spend 15.9s (59%) in the database. Test databases don't need to survive a crash, so the server can skip flushing to disk.

High Database

3.18 s per run

Fix: For a PostgreSQL test server (Docker/CI service) start it with -c fsync=off -c synchronous_commit=off -c full_page_writes=off, and put its data directory on tmpfs; for MySQL use --innodb-flush-log-at-trx-commit=0 --skip-log-bin. Never on a server with data you need. Read the guide

Details

Only affects crash safety of the throwaway test server; query behaviour is identical.

Where:

apps/projects/models.py:466 Profile.save · 330 ms
apps/projects/profiles.py:334 write_snapshots · 197 ms
apps/api/tests.py:76 IngestStartEndpointTest.join_workers · 183 ms
apps/projects/environments.py:63 get_or_create_environment · 177 ms
apps/projects/tests.py:954 ProjectPagesTest.setUp · 169 ms
apps/projects/models.py:18 get_or_create_numbered · 168 ms
apps/orgs/views.py:33 org_shell · 167 ms
apps/projects/urls.py:49 find_project · 158 ms
apps/projects/profiles.py:479 write_perfs · 153 ms
apps/api/urls.py:59 touch_token · 150 ms

Most affected tests:

apps/api/tests.py::TestApiIndex::test_index
apps/projects/tests.py::SeedDemoCommandTest::test_seed_demo
apps/projects/tests.py::ProjectPagesTest::test_configure_page
apps/projects/tests.py::ProjectPagesTest::test_dashboard_filters
apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_progress_end
apps/api/tests.py::IngestStartEndpointTest::test_ingest_progress_before_start
apps/api/tests.py::IngestStartEndpointTest::test_all_test_status_types
apps/projects/tests.py::ProfilePagePaginationTest::test_slowest_tests_first_then_the_next_page

Documentation

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.

High Database

2.87 s per run

Fix: Django: fetch related rows in one query with select_related() for foreign keys and prefetch_related() for reverse/many-to-many relations, then lock the count in with assertNumQueries (or pytest-django's django_assert_num_queries). Read the guide

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

Documentation

Stop re-running migrations on every test run

Migrations take 3.2s per run, before the first test can start.

High Migrations

2.84 s per run

Fix: Run with --reuse-db (add it to addopts in pytest.ini/pyproject) so the test database survives between runs; pass --create-db when migrations change. If no test depends on data migrations, --nomigrations builds the schema straight from the models, which is faster still. Read the guide

Details

CI should still build the database from scratch (no --reuse-db) so broken migrations are caught.

Where:

apps/projects/migrations/0012_backfill_session_environments.py:30 backfill · 3 ms
apps/projects/migrations/0014_backfill_session_counts.py:23 backfill · 3 ms
apps/projects/migrations/0016_profile_parts.py:9 move_documents · 3 ms
apps/projects/migrations/0012_backfill_session_environments.py:24 backfill · 1 ms
apps/projects/migrations/0014_backfill_session_counts.py:15 backfill.<locals>.count · 1 ms
apps/projects/migrations/0015_store_compressed_documents_as_is.py:12 external_storage · 1 ms
apps/projects/migrations/0016_profile_parts.py:24 external_storage · 1 ms
apps/projects/migrations/0022_backfill_organizations.py:48 forwards · 1 ms
apps/projects/migrations/0022_backfill_organizations.py:69 forwards · 1 ms
apps/projects/migrations/0025_backfill_slugs_and_numbers.py:28 forwards · 1 ms

Most affected tests:

apps/api/tests.py::TestApiIndex::test_index

Documentation

Use a fast password hasher in tests

2.4s (9% of test time) is spent hashing passwords. Slow hashing protects real passwords; in tests it only burns CPU.

Medium Password hashing

2.25 s per run

Fix: In your test settings set PASSWORD_HASHERS = ["django.contrib.auth.hashers.MD5PasswordHasher"] (currently PBKDF2PasswordHasher). Read the guide

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 · 470 ms
apps/orgs/tests.py:194 SuperuserTest.test_superusers_can_open_any_project_but_dont_list_them · 438 ms
ft/tests.py:231 TestAccountSettings.test_projects_only_lists_your_own_even_for_superusers · 264 ms
apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 255 ms
ft/tests.py:199 TestAccountSettings.test_change_password · 250 ms
ft/tests.py:160 TestAccountPages.test_signup · 241 ms
ft/tests.py:214 TestAccountSettings.test_change_password · 234 ms
ft/tests.py:176 TestAccountSettings.setUpTestData · 221 ms

Most affected tests:

ft/tests.py::TestAccountSettings::test_change_password
apps/orgs/tests.py::SuperuserTest::test_superusers_can_open_any_project_but_dont_list_them
ft/tests.py::TestAccountSettings::test_projects_only_lists_your_own_even_for_superusers
apps/orgs/tests.py::SignupTest::test_signing_up_creates_an_organization
ft/tests.py::TestAccountPages::test_signup

Documentation

pytest takes a long time before the first test runs

Startup takes 4.8s and collection 392ms on every run, even when you only run one test.

Medium Imports

2.09 s per run

Fix: Set testpaths and norecursedirs (node_modules, .venv, build, docs) so pytest doesn't walk unrelated directories; move heavy imports out of module level in test files and conftest.py into fixtures; check `python -X importtime -m pytest --collect-only -q` for the slowest imports. Read the guide

Details

.venv/bin/pytest (392ms)
.venv/bin/pytest (4.8s)

Documentation

Use TestCase instead of TransactionTestCase

1.0s goes to flushing every table after tests in 11 TransactionTestCase / transaction=True / live_server tests.

Medium DB schema

901 ms per run

Fix: Use django.test.TestCase (or @pytest.mark.django_db without transaction=True): it wraps each test in a transaction and rolls back instead of truncating every table. Keep TransactionTestCase only for tests that need real commits (on_commit hooks can use TestCase.captureOnCommitCallbacks). Read the guide

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::ProfileUploadLockTest::test_upload_while_a_part_is_being_processed
apps/api/tests.py::ProfileUploadQueueTest::test_upload_is_processed_by_the_worker
apps/api/tests.py::IngestStartEndpointTest::test_ingest_multiple_sessions
apps/api/tests.py::IngestStartEndpointTest::test_ingest_progress_before_start
apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_with_git
apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_progress_end
apps/api/tests.py::IngestStartEndpointTest::test_ingest_valid
apps/api/tests.py::IngestStartEndpointTest::test_all_test_status_types

Documentation

Tests open new database connections over and over

Connecting to the database takes 968ms.

Low Database

775 ms per run

Fix: Reuse connections: create the engine once per session (not per test) and keep the default pool (NullPool reconnects on every checkout); in Django avoid closing connections in tests (connection.close()/close_old_connections). Read the guide

Details

Where:

apps/api/tests.py:76 IngestStartEndpointTest.join_workers · 164 ms
apps/api/tests.py:73 IngestStartEndpointTest.setUp · 99 ms
apps/api/tasks.py:266 warm_reports · 61 ms
apps/api/urls.py:72 api_request.<locals>.decorator.<locals>.wrapped_view · 48 ms
apps/api/tests.py:306 IngestStartEndpointTest.test_details_are_kept_for_failures_only · 12 ms
apps/api/tests.py:988 ProfileUploadQueueTest.test_upload_is_processed_by_the_worker · 12 ms
apps/api/tasks.py:237 process_profile · 12 ms
apps/api/tests.py:287 IngestStartEndpointTest.test_all_test_status_types · 10 ms
apps/api/tests.py:235 IngestStartEndpointTest.test_ingest_progress_before_start · 10 ms
apps/api/tests.py:928 ProfileUploadLockTest.setUp · 10 ms

Most affected tests:

apps/api/tests.py::IngestStartEndpointTest::test_ingest_progress_before_start
apps/api/tests.py::IngestStartEndpointTest::test_all_test_status_types
apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_progress_end
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::ProfileUploadQueueTest::test_upload_is_processed_by_the_worker
apps/api/tests.py::IngestStartEndpointTest::test_details_are_kept_for_failures_only
apps/api/tests.py::IngestStartEndpointTest::test_ingest_valid

Create shared test data in setUpTestData instead of setUp

setUp() runs before every test and takes 907ms in total (db 828ms, library 57ms, copying 10ms) in 14 classes: SettingsTest (3 tests), ProjectsPageTest (5 tests), ProjectEditPage (6 tests), ProjectDeletePage (4 tests).

Low Database

635 ms per run

Fix: Move object creation that tests only read from setUp() into `@classmethod def setUpTestData(cls)`: it runs once per class and each test still sees the original rows (TestCase rolls back to a savepoint). Read the guide

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 · 195 ms
apps/api/tests.py:73 IngestStartEndpointTest.setUp · 149 ms
apps/projects/tests.py:101 ProjectsPageTest.setUp · 81 ms
apps/projects/tests.py:413 TestProjectTestPage.setUp · 59 ms
apps/projects/tests.py:269 ProjectRunsPage.setUp · 55 ms
apps/projects/tests.py:338 ProjectTestsPage.setUp · 53 ms
ft/tests.py:180 TestAccountSettings.setUp · 53 ms
apps/projects/tests.py:143 ProjectEditPage.setUp · 50 ms
apps/projects/tests.py:188 ProjectDeletePage.setUp · 41 ms
apps/projects/tests.py:219 ProjectCreatePage.setUp · 39 ms

Most affected tests:

apps/projects/tests.py::ProjectsPageTest::test_other_peoples_project
apps/projects/tests.py::TestProjectTestPage::test_other_peoples_project
apps/projects/tests.py::ProjectTestsPage::test_project_with_no_tests
apps/api/tests.py::IngestStartEndpointTest::test_ingest_valid
ft/tests.py::TestAccountSettings::test_connections
apps/projects/tests.py::ProjectsPageTest::test_not_logged_in
apps/projects/tests.py::UnstorableCharactersTest::test_test_page_renders_a_stored_lone_surrogate
apps/api/tests.py::IngestStartEndpointTest::test_all_test_status_types

Documentation

Tests

201–253 of 253, slowest first · click a column to sort this page

Test	Outcome	Duration	Setup	Call	Teardown	Mostly	Queries
apps/projects/tests.py::StorageTest::test_reprocessing_a_profile_replaces_its_contribution	passed	34 ms	0.69 ms	33 ms	0.20 ms	Database	47 12 repeated
apps/api/tests.py::ProfileUploadTest::test_reject_invalid_json	passed	34 ms	0.85 ms	33 ms	0.14 ms	Libraries	10
apps/guides/tests.py::TestContent::test_links_to_the_site_resolve	passed	29 ms	0.67 ms	28 ms	0.17 ms	pytest	5
apps/projects/tests.py::AnalyticsTest::test_slow_tests_per_environment	passed	28 ms	0.80 ms	27 ms	0.16 ms	Database	24 13 repeated
apps/projects/tests.py::SlugsAndNumbersTest::test_a_taken_number_is_retried	passed	26 ms	16 ms	11 ms	0.14 ms	Database	24 3 repeated
apps/projects/tests.py::AnalyticsTest::test_single_test	passed	22 ms	0.62 ms	22 ms	0.15 ms	Database	16 9 repeated
apps/projects/tests.py::AnalyticsTest::test_overview	passed	19 ms	0.63 ms	18 ms	0.12 ms	Database	17
apps/orgs/tests.py::SignupTest::test_github_login_names_it	passed	17 ms	9 ms	8 ms	0.12 ms	Database	11
apps/orgs/tests.py::SlugTest::test_unique_and_not_reserved	passed	17 ms	10 ms	6 ms	0.55 ms	Database	11 5 repeated
apps/guides/tests.py::TestContent::test_an_insight_has_one_guide	passed	17 ms	11 ms	6 ms	0.17 ms	Database	5
apps/projects/tests.py::SlugsAndNumbersTest::test_runs_and_profiles_are_numbered_per_project	passed	17 ms	0.65 ms	16 ms	0.18 ms	Database	23 6 repeated
apps/projects/tests.py::RealProfileDocumentTest::test_processed	passed	15 ms	0.66 ms	14 ms	1 ms	Database	13 3 repeated
apps/projects/tests.py::MemoryTest::test_stored_and_summed_per_day	passed	14 ms	0.88 ms	12 ms	1 ms	Database	23
apps/projects/tests.py::MemoryTest::test_memory_tests_are_ranked_by_average_peak	passed	13 ms	0.68 ms	13 ms	0.14 ms	Database	22
apps/projects/tests.py::AnalyticsTest::test_ci_vs_local	passed	13 ms	0.71 ms	13 ms	0.12 ms	Database	13
apps/projects/tests.py::FlakyReportTest::test_report_by_environment_kind	passed	13 ms	0.69 ms	12 ms	0.13 ms	Database	14
apps/projects/tests.py::RealProfileDocumentTest::test_entry_details	passed	13 ms	1 ms	11 ms	0.29 ms	Database	5
apps/projects/tests.py::SlugsAndNumbersTest::test_upsert_keeps_slugs_and_makes_them_unique	passed	12 ms	0.68 ms	11 ms	0.50 ms	Database	16 6 repeated
apps/projects/tests.py::FlakyReportTest::test_window	passed	12 ms	0.69 ms	10 ms	0.87 ms	Database	13
apps/api/tests.py::ProfileUploadTest::test_processing_failure_is_recorded	passed	12 ms	0.70 ms	11 ms	0.13 ms	Database	15 3 repeated
apps/projects/tests.py::AnalyticsTest::test_compare_environments	passed	12 ms	0.65 ms	11 ms	0.12 ms	Database	11
apps/projects/tests.py::ClassifyStreaksTest::test_dirty_runs_are_not_the_same_commit	passed	11 ms	9 ms	2 ms	0.16 ms	Database	5
apps/projects/tests.py::FlakyReportTest::test_single_test	passed	11 ms	0.62 ms	10 ms	0.16 ms	Database	11
apps/projects/tests.py::AnalyticsTest::test_slow_tests	passed	10 ms	0.72 ms	10 ms	0.18 ms	Database	10
apps/projects/tests.py::StorageTest::test_slow_tests_come_from_daily_stats	passed	10 ms	0.72 ms	9 ms	0.15 ms	Database	11
apps/guides/tests.py::TestContent::test_front_matter	passed	10 ms	0.63 ms	9 ms	0.19 ms	pytest	5
apps/projects/tests.py::AnalyticsTest::test_fix_next	passed	10 ms	0.76 ms	9 ms	0.13 ms	Database	8
apps/projects/tests.py::AnalyticsTest::test_resolve_scope	passed	8 ms	0.62 ms	8 ms	0.12 ms	Database	11 6 repeated
apps/projects/tests.py::StorageTest::test_snapshot_renders_like_the_whole_document	passed	8 ms	0.69 ms	7 ms	0.57 ms	Database	9
apps/projects/tests.py::AnalyticsTest::test_environment_rows	passed	7 ms	0.66 ms	7 ms	0.17 ms	Database	8
apps/projects/tests.py::AnalyticsTest::test_ci_vs_local_needs_both	passed	7 ms	0.58 ms	6 ms	0.11 ms	Database	9
apps/projects/tests.py::StorageTest::test_daily_stats_sum_the_days_results	passed	6 ms	0.74 ms	5 ms	0.13 ms	Database	8
apps/guides/tests.py::TestContent::test_every_insight_has_a_guide	passed	6 ms	0.69 ms	5 ms	0.17 ms	Database	5
apps/projects/tests.py::AnalyticsTest::test_suite_trend	passed	5 ms	0.59 ms	4 ms	0.51 ms	Database	6
apps/projects/tests.py::RealProfileDocumentTest::test_flat_stacks_still_work	passed	5 ms	0.73 ms	4 ms	0.11 ms	Database	5
apps/guides/tests.py::TestContent::test_unknown_insights	passed	3 ms	0.68 ms	1 ms	0.62 ms	Database	5
apps/projects/tests.py::SlugsAndNumbersTest::test_test_slugs_read_like_their_node_ids	passed	3 ms	0.80 ms	2 ms	0.17 ms	Database	5
apps/projects/tests.py::ClassifyStreaksTest::test_resolved_without_changed_files	passed	2 ms	1 ms	1 ms	0.11 ms	Database	5
apps/projects/tests.py::ClassifyStreaksTest::test_test_changed_when_the_test_file_changed	passed	2 ms	0.61 ms	1 ms	0.48 ms	Database	5
apps/projects/tests.py::ClassifyStreaksTest::test_flaky_when_failed_and_passed_on_same_commit	passed	2 ms	0.61 ms	2 ms	0.13 ms	Database	5
apps/projects/tests.py::ClassifyStreaksTest::test_environment_kinds_are_counted	passed	2 ms	0.66 ms	1 ms	0.11 ms	Database	5
apps/projects/tests.py::ClassifyStreaksTest::test_multiple_streaks_in_order	passed	2 ms	0.63 ms	1 ms	0.14 ms	Database	5
apps/projects/tests.py::ClassifyStreaksTest::test_flaky_even_if_the_pass_came_first_and_elsewhere	passed	2 ms	0.60 ms	1 ms	0.11 ms	Database	5
apps/projects/tests.py::ClassifyStreaksTest::test_no_failures	passed	2 ms	0.60 ms	1 ms	0.11 ms	Unsampled	5
apps/projects/tests.py::ClassifyStreaksTest::test_regression_caught_when_app_code_fixed_it	passed	2 ms	0.60 ms	1 ms	0.11 ms	Database	5
apps/projects/tests.py::ClassifyStreaksTest::test_ongoing	passed	2 ms	0.59 ms	1 ms	0.11 ms	Unsampled	5
apps/projects/tests.py::ClassifyStreaksTest::test_test_changed_matches_paths_relative_to_the_repository	passed	2 ms	0.58 ms	1 ms	0.11 ms	Database	5
apps/projects/tests.py::MigrationInsightsTest::test_per_runner	passed	2 ms	1 ms	0.30 ms	0.17 ms	Unsampled	–
apps/projects/tests.py::MigrationInsightsTest::test_per_runner_needs_several_runners	passed	1 ms	0.86 ms	0.16 ms	0.11 ms	pytest	–
apps/projects/tests.py::MigrationInsightsTest::test_per_worker	passed	1 ms	0.71 ms	0.26 ms	0.11 ms	Unsampled	–
apps/projects/tests.py::MigrationInsightsTest::test_per_worker_ignores_cheap_setups	passed	0.97 ms	0.70 ms	0.16 ms	0.11 ms	Unsampled	–
apps/projects/tests.py::MigrationInsightsTest::test_per_worker_needs_repeated_builds	passed	0.89 ms	0.61 ms	0.17 ms	0.11 ms	Unsampled	–
apps/projects/tests.py::MigrationInsightsTest::test_per_worker_tolerates_bad_fixture_data	passed	0.88 ms	0.61 ms	0.17 ms	0.11 ms	Unsampled	–

Page 2 of 2 Previous

Memory

The test process peaked at 211 MB

Needed the most memory	Needed	Kept after
apps/api/tests.py::TestApiIndex::test_index	32 MB	32 MB
apps/api/tests.py::ProfileUploadTest::test_missing_parts_mark_the_profile_incomplete	3 MB	3 MB
apps/projects/tests.py::ProfilePagePaginationTest::test_slowest_tests_first_then_the_next_page	2 MB	2 MB
apps/orgs/tests.py::SignupTest::test_signing_up_creates_an_organization	992 KB	992 KB
ft/tests.py::TestAccountPages::test_static_pages	932 KB	932 KB
ft/tests.py::TestAccountSettings::test_email	928 KB	928 KB
apps/projects/tests.py::ProjectRunsPage::test_project_with_runs	900 KB	900 KB
apps/projects/tests.py::ProjectRunPage::test_not_logged_in	872 KB	872 KB
apps/orgs/tests.py::AccessTest::test_members_see_every_project_of_the_organization	868 KB	868 KB
ft/tests.py::TestAccountPages::test_signup	868 KB	868 KB

Slowest fixtures

Exact setup time across the session

Fixture	Scope	Calls	Total	Max
_django_setup_unittest	class	54	3.41 s	3.40 s
django_db_setup	session	1	3.39 s	3.39 s
_unittest_setUpClass_fixture_ProjectPagesTest	class	1	256 ms	256 ms
_unittest_setUpClass_fixture_TestAccountSettings	class	1	239 ms	239 ms
_unittest_setUpClass_fixture_ProfilePagePaginationTest	class	1	202 ms	202 ms
_unittest_setUpClass_fixture_McpTest	class	1	171 ms	171 ms
_unittest_setUpClass_fixture_AnalyticsTest	class	1	165 ms	165 ms
_unittest_setUpClass_fixture_RealProfileDocumentTest	class	1	127 ms	127 ms
_unittest_setUpClass_fixture_MemoryTest	class	1	84 ms	84 ms
_unittest_setUpClass_fixture_StorageTest	class	1	78 ms	78 ms
_unittest_setUpClass_fixture_FlakyReportTest	class	1	64 ms	64 ms
_unittest_setUpClass_fixture_LegacyUrlTest	class	1	59 ms	59 ms
_unittest_setUpClass_fixture_UnstorableCharactersTest	class	1	50 ms	50 ms
_unittest_setUpClass_fixture_FlakyReportCacheTest	class	1	49 ms	49 ms
_unittest_setUpClass_fixture_SuperuserTest	class	1	22 ms	22 ms