flakytest.dev anze3db flakytest
Profiles / #13

Passed Run of Nov 9, 00:14

CI github-actions:test · 19dac9b main dirty · pass/fail report
Some tests got too few samples to explain their time. Rerun with pytest --flakytest-profile --flakytest-rate 5000.
Wall time
21.56 s
1 worker
Test time
17.43 s
sum of test durations
Tests
254
254 passed
Profiler
tachyon
1000 Hz · 16,184 samples · Python 3.15.2 · flakytest 2026.0b1
Peak memory
180 MB
test process

Where the time goes

Test time by category
  • Database7.35 s
  • Libraries2.89 s
  • Migrations2.83 s
  • DB schema1.44 s
  • Password hashing1.21 s
  • Templates519 ms
  • Imports300 ms
  • Deep copies264 ms
  • App code175 ms
  • Serialization163 ms
  • Unsampled161 ms
  • pytest70 ms
  • Test code17 ms
  • Factories12 ms
  • Waiting9 ms
  • Cache8 ms
  • Logging7 ms
  • Mocking6 ms

Session timeline

Tests
16.79 s
Startup
3.51 s
Collection
175 ms
Between tests
526 ms
Session teardown
451 ms
Test phases
Setup 4.99 s Call 12.32 s Teardown 118 ms

Fix next

Ranked by the time each fix saves per run
1

Use plain static file storage in tests

Static file storage/manifest handling costs 6.5s.

High App code
6.50 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 · 342 ms
  • apps/guides/content.py:112 render · 263 ms
  • ft/tests.py:204 TestAccountSettings.test_change_password · 261 ms
  • apps/mcp/tests.py:67 McpTest.post · 247 ms
  • apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 178 ms
  • apps/projects/tests.py:320 ProjectRunPage.test_other_peoples_project · 156 ms
  • apps/orgs/tests.py:70 AccessTest.test_others_dont · 151 ms
  • ft/tests.py:160 TestAccountPages.test_signup · 147 ms
  • ft/tests.py:199 TestAccountSettings.test_change_password · 131 ms
  • apps/orgs/views.py:33 org_shell · 128 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
  • apps/api/tests.py::TestApiIndex::test_index
  • apps/projects/tests.py::ProjectRunPage::test_other_peoples_project
  • ft/tests.py::TestAccountPages::test_signup
  • apps/orgs/tests.py::AccessTest::test_others_dont
2

Disable django-debug-toolbar in tests

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

High App code
4.17 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:

  • apps/guides/content.py:112 render · 263 ms
  • ft/tests.py:204 TestAccountSettings.test_change_password · 261 ms
  • apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 171 ms
  • ft/tests.py:160 TestAccountPages.test_signup · 147 ms
  • ft/tests.py:199 TestAccountSettings.test_change_password · 131 ms
  • apps/orgs/views.py:33 org_shell · 128 ms
  • apps/api/urls.py:72 api_request.<locals>.decorator.<locals>.wrapped_view · 127 ms
  • ft/urls.py:35 <module> · 119 ms
  • apps/orgs/models.py:65 Organization.is_owner · 114 ms
  • apps/api/urls.py:59 touch_token · 91 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/api/tests.py::ProfileUploadTest::test_upload_adds_migrations_per_worker_insight
  • apps/projects/tests.py::ProfilePagePaginationTest::test_slowest_tests_first_then_the_next_page

Documentation

3

Stop re-running migrations on every test run

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

High Migrations
2.54 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 · 2 ms
  • apps/projects/migrations/0012_backfill_session_environments.py:24 backfill · 1 ms
  • apps/projects/migrations/0015_store_compressed_documents_as_is.py:12 external_storage · 1 ms
  • apps/projects/migrations/0018_profile_stats_applied.py:9 mark_applied · 1 ms
  • apps/projects/migrations/0022_backfill_organizations.py:48 forwards · 1 ms
  • apps/projects/migrations/0025_backfill_slugs_and_numbers.py:28 forwards · 1 ms
  • apps/projects/migrations/0025_backfill_slugs_and_numbers.py:35 forwards · 1 ms

Most affected tests:

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

Documentation

4

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.50 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

5

Make the test database server skip durability work

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

High Database
2.32 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 · 228 ms
  • apps/projects/profiles.py:497 write_perfs · 199 ms
  • apps/projects/tests.py:954 ProjectPagesTest.setUp · 131 ms
  • apps/orgs/views.py:33 org_shell · 128 ms
  • apps/api/urls.py:72 api_request.<locals>.decorator.<locals>.wrapped_view · 125 ms
  • apps/projects/rollups.py:88 add_perfs · 125 ms
  • apps/api/tests.py:76 IngestStartEndpointTest.join_workers · 120 ms
  • apps/projects/environments.py:63 get_or_create_environment · 116 ms
  • apps/projects/profiles.py:352 write_snapshots · 115 ms
  • apps/orgs/models.py:65 Organization.is_owner · 111 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_all_test_status_types
  • apps/api/tests.py::IngestStartEndpointTest::test_results_are_counted_and_the_payload_dropped
  • apps/api/tests.py::IngestStartEndpointTest::test_ingest_progress_before_start
  • apps/api/tests.py::IngestStartEndpointTest::test_ingest_end_after_progress

Documentation

6

pytest takes a long time before the first test runs

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

Medium Imports
1.47 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 (175ms)
  • .venv/bin/pytest (3.5s)

Documentation

7

Use a fast password hasher in tests

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

Medium Password hashing
1.15 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 · 258 ms
  • apps/orgs/tests.py:194 SuperuserTest.test_superusers_can_open_any_project_but_dont_list_them · 144 ms
  • ft/tests.py:231 TestAccountSettings.test_projects_only_lists_your_own_even_for_superusers · 144 ms
  • ft/tests.py:160 TestAccountPages.test_signup · 142 ms
  • apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 140 ms
  • ft/tests.py:214 TestAccountSettings.test_change_password · 130 ms
  • ft/tests.py:199 TestAccountSettings.test_change_password · 129 ms
  • ft/tests.py:176 TestAccountSettings.setUpTestData · 123 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
  • ft/tests.py::TestAccountPages::test_signup
  • apps/orgs/tests.py::SignupTest::test_signing_up_creates_an_organization

Documentation

8

Use TestCase instead of TransactionTestCase

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

Medium DB schema
675 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::IngestStartEndpointTest::test_ingest_start_with_git
  • apps/api/tests.py::IngestStartEndpointTest::test_details_are_kept_for_failures_only
  • apps/api/tests.py::IngestStartEndpointTest::test_ingest_progress_before_start
  • 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_start_progress_end
  • apps/api/tests.py::ProfileUploadLockTest::test_upload_while_a_part_is_being_processed
  • apps/api/tests.py::IngestStartEndpointTest::test_results_are_counted_and_the_payload_dropped

Documentation

9

Tests open new database connections over and over

Connecting to the database takes 723ms.

Medium Database
578 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 · 110 ms
  • apps/api/tests.py:73 IngestStartEndpointTest.setUp · 68 ms
  • apps/api/tasks.py:266 warm_reports · 43 ms
  • apps/api/urls.py:72 api_request.<locals>.decorator.<locals>.wrapped_view · 34 ms
  • apps/api/tests.py:287 IngestStartEndpointTest.test_all_test_status_types · 14 ms
  • apps/api/tests.py:306 IngestStartEndpointTest.test_details_are_kept_for_failures_only · 8 ms
  • apps/api/tests.py:975 ProfileUploadQueueTest.setUp · 8 ms
  • apps/api/tests.py:257 IngestStartEndpointTest.test_ingest_end_after_progress · 7 ms
  • apps/api/tasks.py:237 process_profile · 6 ms
  • apps/api/tests.py:988 ProfileUploadQueueTest.test_upload_is_processed_by_the_worker · 6 ms

Most affected tests:

  • apps/api/tests.py::IngestStartEndpointTest::test_all_test_status_types
  • apps/api/tests.py::IngestStartEndpointTest::test_ingest_end_after_progress
  • apps/api/tests.py::IngestStartEndpointTest::test_ingest_progress_before_start
  • apps/api/tests.py::IngestStartEndpointTest::test_results_are_counted_and_the_payload_dropped
  • apps/mcp/tests.py::McpTest::test_bare_token
  • apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_progress_end
  • apps/api/tests.py::ProfileUploadQueueTest::test_upload_is_processed_by_the_worker
  • apps/api/tests.py::IngestStartEndpointTest::test_details_are_kept_for_failures_only
10

Create shared test data in setUpTestData instead of setUp

setUp() runs before every test and takes 642ms in total (db 610ms, library 18ms, serialization 10ms) in 14 classes: SettingsTest (3 tests), ProjectsPageTest (5 tests), ProjectEditPage (6 tests), ProjectDeletePage (4 tests).

Low Database
449 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 · 140 ms
  • apps/api/tests.py:73 IngestStartEndpointTest.setUp · 105 ms
  • apps/projects/tests.py:338 ProjectTestsPage.setUp · 62 ms
  • apps/projects/tests.py:143 ProjectEditPage.setUp · 45 ms
  • apps/projects/tests.py:101 ProjectsPageTest.setUp · 38 ms
  • apps/projects/tests.py:413 TestProjectTestPage.setUp · 36 ms
  • apps/projects/tests.py:1429 MemoryTest.setUp · 36 ms
  • apps/orgs/tests.py:167 SettingsTest.setUp · 27 ms
  • apps/projects/tests.py:269 ProjectRunsPage.setUp · 27 ms
  • apps/projects/tests.py:219 ProjectCreatePage.setUp · 27 ms

Most affected tests:

  • apps/projects/tests.py::ProjectTestsPage::test_other_peoples_project
  • apps/orgs/tests.py::SettingsTest::test_delete
  • apps/projects/tests.py::ProjectEditPage::test_project
  • apps/projects/tests.py::ProjectTestsPage::test_project_with_no_tests
  • apps/projects/tests.py::ProjectsPageTest::test_not_logged_in
  • apps/projects/tests.py::ProjectEditPage::test_project_submit
  • apps/api/tests.py::IngestStartEndpointTest::test_ingest_valid
  • apps/api/tests.py::IngestStartEndpointTest::test_results_are_counted_and_the_payload_dropped

Documentation

Tests

201–254 of 254, slowest first · click a column to sort this page
Test Outcome Duration Setup Call Teardown Mostly Queries
apps/mcp/tests.py::McpTest::test_get_not_allowed
passed 18 ms 0.37 ms 17 ms 0.08 ms Libraries 5
apps/api/tests.py::ProfileUploadTest::test_get_not_allowed
passed 18 ms 0.39 ms 17 ms 0.11 ms Libraries 5
apps/mcp/tests.py::McpTest::test_ping
passed 17 ms 0.38 ms 17 ms 0.08 ms Libraries 7
apps/projects/tests.py::AnalyticsTest::test_single_test
passed 17 ms 0.36 ms 16 ms 0.25 ms Database 16
9 repeated
apps/api/tests.py::ProfileUploadTest::test_no_token
passed 17 ms 0.39 ms 16 ms 0.08 ms Libraries 6
apps/mcp/tests.py::McpTest::test_initialize
passed 17 ms 0.37 ms 16 ms 0.08 ms Libraries 7
apps/guides/tests.py::TestContent::test_links_to_the_site_resolve
passed 15 ms 0.34 ms 15 ms 0.09 ms Libraries 5
apps/guides/tests.py::TestGuidePages::test_old_mute_page_redirects
passed 15 ms 0.44 ms 15 ms 0.08 ms Libraries 5
apps/projects/tests.py::AnalyticsTest::test_overview
passed 13 ms 0.37 ms 12 ms 0.08 ms Database 17
apps/orgs/tests.py::SignupTest::test_github_login_names_it
passed 12 ms 6 ms 5 ms 0.09 ms Database 11
apps/orgs/tests.py::SlugTest::test_unique_and_not_reserved
passed 11 ms 7 ms 4 ms 0.28 ms Database 11
5 repeated
apps/projects/tests.py::AnalyticsTest::test_compare_environments
passed 11 ms 0.35 ms 11 ms 0.08 ms Database 11
apps/projects/tests.py::SlugsAndNumbersTest::test_runs_and_profiles_are_numbered_per_project
passed 10 ms 0.36 ms 10 ms 0.08 ms Database 23
6 repeated
apps/projects/tests.py::FlakyReportTest::test_report_by_environment_kind
passed 10 ms 0.31 ms 9 ms 0.08 ms Database 14
apps/projects/tests.py::StorageTest::test_slow_tests_come_from_daily_stats
passed 10 ms 0.42 ms 9 ms 0.11 ms Database 11
apps/guides/tests.py::TestContent::test_an_insight_has_one_guide
passed 10 ms 6 ms 3 ms 0.09 ms Database 5
apps/projects/tests.py::AnalyticsTest::test_ci_vs_local
passed 9 ms 0.39 ms 9 ms 0.10 ms Database 13
apps/projects/tests.py::RealProfileDocumentTest::test_entry_details
passed 9 ms 0.42 ms 8 ms 0.21 ms Deep copies 5
apps/projects/tests.py::MemoryTest::test_memory_tests_are_ranked_by_average_peak
passed 8 ms 0.35 ms 8 ms 0.08 ms Database 22
apps/projects/tests.py::AnalyticsTest::test_slow_tests
passed 8 ms 0.41 ms 8 ms 0.10 ms Database 10
apps/projects/tests.py::MemoryTest::test_stored_and_summed_per_day
passed 8 ms 0.39 ms 8 ms 0.35 ms Database 23
apps/projects/tests.py::StorageTest::test_snapshot_renders_like_the_whole_document
passed 8 ms 0.43 ms 6 ms 1 ms Database 9
apps/projects/tests.py::SlugsAndNumbersTest::test_upsert_keeps_slugs_and_makes_them_unique
passed 8 ms 0.34 ms 7 ms 0.31 ms Database 16
6 repeated
apps/projects/tests.py::ClassifyStreaksTest::test_dirty_runs_are_not_the_same_commit
passed 8 ms 6 ms 1 ms 0.07 ms Database 5
apps/projects/tests.py::FlakyReportTest::test_window
passed 7 ms 0.41 ms 7 ms 0.35 ms Database 13
apps/projects/tests.py::FlakyReportTest::test_single_test
passed 7 ms 0.33 ms 7 ms 0.08 ms Database 11
apps/api/tests.py::ProfileUploadTest::test_processing_failure_is_recorded
passed 7 ms 0.38 ms 6 ms 0.09 ms Database 15
3 repeated
apps/guides/tests.py::TestContent::test_front_matter
passed 6 ms 0.40 ms 5 ms 0.10 ms pytest 5
apps/projects/tests.py::AnalyticsTest::test_resolve_scope
passed 5 ms 0.41 ms 5 ms 0.09 ms Database 11
6 repeated
apps/projects/tests.py::AnalyticsTest::test_fix_next
passed 5 ms 0.30 ms 5 ms 0.08 ms Database 8
apps/projects/tests.py::AnalyticsTest::test_environment_rows
passed 4 ms 0.39 ms 4 ms 0.08 ms Database 8
apps/projects/tests.py::AnalyticsTest::test_ci_vs_local_needs_both
passed 4 ms 0.38 ms 4 ms 0.09 ms Database 9
apps/projects/tests.py::AnalyticsTest::test_suite_trend
passed 4 ms 0.38 ms 4 ms 0.39 ms Database 6
apps/projects/tests.py::StorageTest::test_daily_stats_sum_the_days_results
passed 4 ms 0.38 ms 3 ms 0.10 ms Database 8
apps/projects/tests.py::ClassifyStreaksTest::test_ongoing
passed 3 ms 0.35 ms 3 ms 0.08 ms Database 5
apps/guides/tests.py::TestContent::test_every_insight_has_a_guide
passed 3 ms 0.34 ms 3 ms 0.15 ms Test code 5
apps/projects/tests.py::RealProfileDocumentTest::test_flat_stacks_still_work
passed 3 ms 0.37 ms 3 ms 0.09 ms Unsampled 5
apps/guides/tests.py::TestContent::test_unknown_insights
passed 1 ms 0.37 ms 0.85 ms 0.28 ms Unsampled 5
apps/projects/tests.py::ClassifyStreaksTest::test_test_changed_matches_paths_relative_to_the_repository
passed 1 ms 0.58 ms 0.81 ms 0.07 ms Unsampled 5
apps/projects/tests.py::ClassifyStreaksTest::test_test_changed_when_the_test_file_changed
passed 1 ms 0.35 ms 0.79 ms 0.29 ms Database 5
apps/projects/tests.py::SlugsAndNumbersTest::test_test_slugs_read_like_their_node_ids
passed 1 ms 0.33 ms 0.96 ms 0.08 ms Unsampled 5
apps/projects/tests.py::ClassifyStreaksTest::test_flaky_even_if_the_pass_came_first_and_elsewhere
passed 1 ms 0.33 ms 0.90 ms 0.08 ms Unsampled 5
apps/projects/tests.py::ClassifyStreaksTest::test_regression_caught_when_app_code_fixed_it
passed 1 ms 0.33 ms 0.90 ms 0.07 ms Database 5
apps/projects/tests.py::ClassifyStreaksTest::test_no_failures
passed 1 ms 0.34 ms 0.81 ms 0.13 ms Unsampled 5
apps/projects/tests.py::ClassifyStreaksTest::test_environment_kinds_are_counted
passed 1 ms 0.35 ms 0.85 ms 0.07 ms Database 5
apps/projects/tests.py::ClassifyStreaksTest::test_multiple_streaks_in_order
passed 1 ms 0.33 ms 0.85 ms 0.07 ms Database 5
apps/projects/tests.py::ClassifyStreaksTest::test_resolved_without_changed_files
passed 1 ms 0.34 ms 0.81 ms 0.07 ms Database 5
apps/projects/tests.py::ClassifyStreaksTest::test_flaky_when_failed_and_passed_on_same_commit
passed 1 ms 0.36 ms 0.78 ms 0.07 ms Database 5
apps/projects/tests.py::MigrationInsightsTest::test_per_runner
passed 1 ms 0.76 ms 0.17 ms 0.09 ms pytest –
apps/projects/tests.py::MigrationInsightsTest::test_per_worker
passed 0.61 ms 0.39 ms 0.15 ms 0.08 ms Unsampled –
apps/projects/tests.py::MigrationInsightsTest::test_per_runner_needs_several_runners
passed 0.59 ms 0.38 ms 0.13 ms 0.08 ms pytest –
apps/projects/tests.py::MigrationInsightsTest::test_per_worker_ignores_cheap_setups
passed 0.54 ms 0.37 ms 0.11 ms 0.07 ms Unsampled –
apps/projects/tests.py::MigrationInsightsTest::test_per_worker_needs_repeated_builds
passed 0.52 ms 0.34 ms 0.11 ms 0.06 ms Unsampled –
apps/projects/tests.py::MigrationInsightsTest::test_per_worker_tolerates_bad_fixture_data
passed 0.49 ms 0.34 ms 0.09 ms 0.06 ms Unsampled –

Slowest fixtures

Exact setup time across the session
Fixture Scope Calls Total Max
_django_setup_unittest class 54 3.52 s 3.51 s
django_db_setup session 1 3.51 s 3.51 s
_unittest_setUpClass_fixture_ProjectPagesTest class 1 220 ms 220 ms
_unittest_setUpClass_fixture_TestAccountSettings class 1 131 ms 131 ms
_unittest_setUpClass_fixture_McpTest class 1 115 ms 115 ms
_unittest_setUpClass_fixture_RealProfileDocumentTest class 1 113 ms 113 ms
_unittest_setUpClass_fixture_AnalyticsTest class 1 109 ms 109 ms
_unittest_setUpClass_fixture_ProfilePagePaginationTest class 1 109 ms 109 ms
_unittest_setUpClass_fixture_MemoryTest class 1 58 ms 58 ms
_unittest_setUpClass_fixture_StorageTest class 1 51 ms 51 ms
_unittest_setUpClass_fixture_FlakyReportTest class 1 46 ms 46 ms
_unittest_setUpClass_fixture_LegacyUrlTest class 1 38 ms 38 ms
_unittest_setUpClass_fixture_UnstorableCharactersTest class 1 32 ms 32 ms
_unittest_setUpClass_fixture_FlakyReportCacheTest class 1 32 ms 32 ms
_unittest_setUpClass_fixture_SettingsTest class 1 15 ms 15 ms