flakytest.dev anze3db flakytest
Profiles / #15

Passed Run of Nov 14, 10:22

CI github-actions:test · cb18ed3 main dirty · pass/fail report
Some tests got too few samples to explain their time. Rerun with pytest --flakytest-profile --flakytest-rate 2000.
Wall time
25.09 s
1 worker
Test time
19.99 s
sum of test durations
Tests
258
258 passed
Profiler
tachyon
1000 Hz · 17,499 samples · Python 3.15.2 · flakytest 2026.0b1
Peak memory
183 MB
test process

Where the time goes

Test time by category
  • Database9.03 s
  • Libraries4.25 s
  • Migrations1.85 s
  • Password hashing1.52 s
  • DB schema938 ms
  • Templates806 ms
  • Imports418 ms
  • App code301 ms
  • Deep copies283 ms
  • Serialization200 ms
  • Unsampled159 ms
  • pytest152 ms
  • Factories29 ms
  • Test code25 ms
  • Waiting17 ms
  • Logging12 ms
  • Mocking4 ms
  • Network3 ms
  • Cache2 ms

Session timeline

Tests
18.75 s
Startup
4.58 s
Collection
304 ms
Between tests
745 ms
Session teardown
560 ms
Test phases
Setup 3.83 s Call 16.05 s Teardown 110 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 9.2s.

High App code
9.16 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 · 491 ms
  • apps/mcp/tests.py:67 McpTest.post · 398 ms
  • ft/tests.py:210 TestAccountSettings.test_change_password · 327 ms
  • apps/guides/content.py:112 render · 319 ms
  • apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 225 ms
  • ft/tests.py:166 TestAccountPages.test_signup · 181 ms
  • ft/tests.py:205 TestAccountSettings.test_change_password · 162 ms
  • apps/projects/tests.py:320 ProjectRunPage.test_other_peoples_project · 156 ms
  • apps/api/urls.py:72 api_request.<locals>.decorator.<locals>.wrapped_view · 153 ms
  • apps/projects/urls.py:692 <module> · 149 ms

Most affected tests:

  • apps/api/tests.py::ProfileUploadTest::test_missing_parts_mark_the_profile_incomplete
  • ft/tests.py::TestAccountSettings::test_change_password
  • apps/projects/tests.py::ProjectPagesTest::test_dashboard_filters
  • 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/api/tests.py::ProfileUploadTest::test_reupload_split_differently
  • apps/projects/tests.py::ProjectRunPage::test_other_peoples_project
2

Disable django-debug-toolbar in tests

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

High App code
5.83 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:210 TestAccountSettings.test_change_password · 327 ms
  • apps/guides/content.py:112 render · 319 ms
  • apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 213 ms
  • ft/tests.py:166 TestAccountPages.test_signup · 181 ms
  • ft/tests.py:205 TestAccountSettings.test_change_password · 162 ms
  • apps/api/urls.py:72 api_request.<locals>.decorator.<locals>.wrapped_view · 153 ms
  • apps/projects/urls.py:692 <module> · 149 ms
  • apps/projects/urls.py:498 project_profile · 136 ms
  • apps/projects/urls.py:40 can_manage_project · 125 ms
  • apps/orgs/views.py:33 org_shell · 115 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
  • ft/tests.py::TestAccountPages::test_signup
  • apps/api/tests.py::ProfileUploadTest::test_upload_adds_migrations_per_worker_insight
  • apps/projects/tests.py::ProjectPagesTest::test_dashboard

Documentation

3

Make the test database server skip durability work

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

High Database
2.36 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:

  • ft/db/postgresql/base.py:39 DatabaseWrapper.get_new_connection · 743 ms
  • apps/projects/models.py:466 Profile.save · 291 ms
  • apps/projects/profiles.py:352 write_snapshots · 155 ms
  • apps/api/urls.py:72 api_request.<locals>.decorator.<locals>.wrapped_view · 151 ms
  • apps/projects/environments.py:63 get_or_create_environment · 134 ms
  • apps/projects/urls.py:40 can_manage_project · 125 ms
  • apps/projects/models.py:230 TestManager.upsert · 123 ms
  • apps/projects/tests.py:954 ProjectPagesTest.setUp · 122 ms
  • apps/projects/rollups.py:88 add_perfs · 121 ms
  • apps/orgs/views.py:33 org_shell · 115 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_ingest_start_progress_end
  • apps/api/tests.py::IngestStartEndpointTest::test_ingest_progress_before_start
  • apps/api/tests.py::IngestStartEndpointTest::test_results_are_counted_and_the_payload_dropped

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

pytest takes a long time before the first test runs

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

Medium Imports
1.95 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 (304ms)
  • .venv/bin/pytest (4.6s)

Documentation

6

Stop re-running migrations on every test run

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

Medium Migrations
1.66 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:

  • ft/db/postgresql/base.py:39 DatabaseWrapper.get_new_connection · 10 ms
  • 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/0004_project_created_by_project_date_created_and_more.py:12 add_created_by_to_project · 2 ms
  • apps/projects/migrations/0016_profile_parts.py:9 move_documents · 2 ms
  • apps/projects/migrations/0016_profile_parts.py:24 external_storage · 2 ms
  • apps/projects/migrations/0018_profile_stats_applied.py:9 mark_applied · 2 ms
  • apps/projects/migrations/0022_backfill_organizations.py:48 forwards · 2 ms
  • apps/projects/migrations/0022_backfill_organizations.py:69 forwards · 2 ms
  • apps/projects/migrations/0025_backfill_slugs_and_numbers.py:28 forwards · 2 ms

Most affected tests:

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

Documentation

7

Use a fast password hasher in tests

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

Medium Password hashing
1.44 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:210 TestAccountSettings.test_change_password · 321 ms
  • ft/tests.py:237 TestAccountSettings.test_projects_only_lists_your_own_even_for_superusers · 187 ms
  • apps/orgs/tests.py:194 SuperuserTest.test_superusers_can_open_any_project_but_dont_list_them · 183 ms
  • apps/orgs/tests.py:28 SignupTest.test_signing_up_creates_an_organization · 179 ms
  • ft/tests.py:166 TestAccountPages.test_signup · 172 ms
  • ft/tests.py:205 TestAccountSettings.test_change_password · 160 ms
  • ft/tests.py:220 TestAccountSettings.test_change_password · 160 ms
  • ft/tests.py:182 TestAccountSettings.setUpTestData · 155 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

Documentation

8

Use TestCase instead of TransactionTestCase

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

Medium DB schema
730 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_valid
  • apps/api/tests.py::IngestStartEndpointTest::test_details_are_kept_for_failures_only
  • apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_with_git
  • apps/api/tests.py::IngestStartEndpointTest::test_all_test_status_types
  • apps/api/tests.py::IngestStartEndpointTest::test_ingest_multiple_sessions
  • apps/api/tests.py::ProfileUploadQueueTest::test_upload_is_processed_by_the_worker
  • apps/api/tests.py::ProfileUploadLockTest::test_upload_while_a_part_is_being_processed
  • apps/api/tests.py::IngestStartEndpointTest::test_ingest_progress_before_start

Documentation

9

Tests open new database connections over and over

Connecting to the database takes 761ms.

Medium Database
609 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:

  • ft/db/postgresql/base.py:39 DatabaseWrapper.get_new_connection · 714 ms
  • apps/api/tests.py:73 IngestStartEndpointTest.setUp · 7 ms
  • apps/api/tests.py:76 IngestStartEndpointTest.join_workers · 7 ms
  • apps/api/urls.py:72 api_request.<locals>.decorator.<locals>.wrapped_view · 3 ms
  • apps/api/tests.py:928 ProfileUploadLockTest.setUp · 1 ms
  • apps/api/tests.py:212 IngestStartEndpointTest.test_ingest_start_progress_end · 1 ms
  • apps/api/tasks.py:266 warm_reports · 1 ms
  • apps/api/tests.py:306 IngestStartEndpointTest.test_details_are_kept_for_failures_only · 1 ms

Most affected tests:

  • 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_ingest_start_progress_end
  • 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_details_are_kept_for_failures_only
  • apps/api/tests.py::ProfileUploadQueueTest::test_upload_is_processed_by_the_worker
  • apps/projects/tests.py::RealProfileDocumentTest::test_call_tree
10

Create shared test data in setUpTestData instead of setUp

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

Low Database
436 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 · 137 ms
  • ft/db/postgresql/base.py:39 DatabaseWrapper.get_new_connection · 75 ms
  • apps/projects/tests.py:143 ProjectEditPage.setUp · 59 ms
  • apps/projects/tests.py:101 ProjectsPageTest.setUp · 54 ms
  • apps/api/tests.py:73 IngestStartEndpointTest.setUp · 41 ms
  • apps/projects/tests.py:219 ProjectCreatePage.setUp · 35 ms
  • apps/projects/tests.py:338 ProjectTestsPage.setUp · 32 ms
  • ft/tests.py:186 TestAccountSettings.setUp · 32 ms
  • apps/projects/tests.py:1429 MemoryTest.setUp · 28 ms
  • apps/projects/tests.py:269 ProjectRunsPage.setUp · 27 ms

Most affected tests:

  • apps/projects/tests.py::ProjectsPageTest::test_other_peoples_project
  • apps/projects/tests.py::ProjectEditPage::test_project_submit
  • apps/api/tests.py::IngestStartEndpointTest::test_ingest_multiple_sessions
  • apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_progress_end
  • apps/projects/tests.py::ProjectsPageTest::test_no_project
  • apps/api/tests.py::ProfileUploadLockTest::test_upload_while_a_part_is_being_processed
  • apps/api/tests.py::IngestStartEndpointTest::test_ingest_start_with_git
  • apps/projects/tests.py::ProjectCreatePage::test_first_project_is_onboarding

Documentation

Tests

201–258 of 258, slowest first · click a column to sort this page
Test Outcome Duration Setup Call Teardown Mostly Queries
apps/mcp/tests.py::McpTest::test_batch_of_notifications
passed 25 ms 0.71 ms 24 ms 0.14 ms Libraries 7
apps/guides/tests.py::TestGuidePages::test_markdown
passed 25 ms 0.58 ms 24 ms 0.17 ms Libraries 5
apps/api/tests.py::ProfileUploadTest::test_reject_too_large_uncompressed
passed 25 ms 0.51 ms 24 ms 0.12 ms Libraries 10
apps/api/tests.py::ProfileUploadTest::test_reject_invalid_json
passed 24 ms 0.53 ms 23 ms 0.11 ms Libraries 10
apps/api/tests.py::ProfileUploadTest::test_reject_missing_run
passed 24 ms 0.56 ms 23 ms 0.14 ms Libraries 10
apps/projects/tests.py::SlugsAndNumbersTest::test_a_taken_number_is_retried
passed 23 ms 14 ms 9 ms 0.11 ms Database 24
3 repeated
apps/guides/tests.py::TestContent::test_links_to_the_site_resolve
passed 21 ms 0.40 ms 20 ms 0.12 ms pytest 5
apps/projects/tests.py::AnalyticsTest::test_overview
passed 19 ms 0.52 ms 18 ms 0.13 ms Database 17
apps/projects/tests.py::RealProfileDocumentTest::test_processed
passed 17 ms 0.50 ms 13 ms 3 ms Database 13
3 repeated
apps/projects/tests.py::AnalyticsTest::test_compare_environments
passed 16 ms 0.52 ms 15 ms 0.12 ms Database 11
apps/orgs/tests.py::SignupTest::test_github_login_names_it
passed 14 ms 7 ms 7 ms 0.12 ms Database 11
apps/projects/tests.py::FlakyReportTest::test_window
passed 14 ms 0.78 ms 10 ms 3 ms Database 13
apps/projects/tests.py::FlakyReportTest::test_report_by_environment_kind
passed 13 ms 0.54 ms 13 ms 0.15 ms Database 14
apps/projects/tests.py::SlugsAndNumbersTest::test_runs_and_profiles_are_numbered_per_project
passed 13 ms 0.50 ms 13 ms 0.12 ms Database 23
6 repeated
apps/orgs/tests.py::SlugTest::test_unique_and_not_reserved
passed 13 ms 7 ms 5 ms 0.34 ms Database 11
5 repeated
apps/projects/tests.py::AnalyticsTest::test_ci_vs_local
passed 12 ms 0.58 ms 12 ms 0.14 ms Database 13
apps/projects/tests.py::FlakyReportTest::test_single_test
passed 12 ms 0.53 ms 11 ms 0.14 ms Database 11
apps/guides/tests.py::TestContent::test_an_insight_has_one_guide
passed 11 ms 7 ms 4 ms 0.12 ms Database 5
apps/projects/tests.py::MemoryTest::test_memory_tests_are_ranked_by_average_peak
passed 11 ms 0.62 ms 10 ms 0.12 ms Database 22
apps/projects/tests.py::MemoryTest::test_stored_and_summed_per_day
passed 10 ms 0.55 ms 9 ms 0.43 ms Database 23
apps/projects/tests.py::ClassifyStreaksTest::test_dirty_runs_are_not_the_same_commit
passed 10 ms 8 ms 2 ms 0.12 ms Database 5
apps/projects/tests.py::SlugsAndNumbersTest::test_upsert_keeps_slugs_and_makes_them_unique
passed 10 ms 0.47 ms 9 ms 0.42 ms Database 16
6 repeated
apps/api/tests.py::ProfileUploadTest::test_processing_failure_is_recorded
passed 9 ms 0.54 ms 9 ms 0.13 ms Database 15
3 repeated
apps/projects/tests.py::StorageTest::test_snapshot_renders_like_the_whole_document
passed 9 ms 0.51 ms 6 ms 3 ms Database 9
apps/projects/tests.py::AnalyticsTest::test_slow_tests
passed 9 ms 0.49 ms 8 ms 0.14 ms Database 10
apps/projects/tests.py::StorageTest::test_slow_tests_come_from_daily_stats
passed 8 ms 0.56 ms 8 ms 0.13 ms Database 11
apps/projects/tests.py::RealProfileDocumentTest::test_entry_details
passed 8 ms 0.58 ms 7 ms 0.37 ms Deep copies 5
apps/guides/tests.py::TestContent::test_front_matter
passed 8 ms 0.41 ms 7 ms 0.10 ms Test code 5
apps/projects/tests.py::AnalyticsTest::test_resolve_scope
passed 8 ms 0.54 ms 7 ms 0.13 ms Database 11
6 repeated
apps/projects/tests.py::AnalyticsTest::test_fix_next
passed 7 ms 0.53 ms 7 ms 0.12 ms Database 8
apps/projects/tests.py::AnalyticsTest::test_environment_rows
passed 7 ms 0.51 ms 6 ms 0.13 ms Database 8
apps/projects/tests.py::AnalyticsTest::test_suite_trend
passed 7 ms 0.50 ms 3 ms 3 ms Unsampled 6
apps/projects/tests.py::AnalyticsTest::test_ci_vs_local_needs_both
passed 6 ms 0.54 ms 5 ms 0.12 ms Database 9
apps/projects/tests.py::StorageTest::test_daily_stats_sum_the_days_results
passed 5 ms 0.51 ms 4 ms 0.12 ms Database 8
apps/guides/tests.py::TestContent::test_every_insight_has_a_guide
passed 4 ms 0.52 ms 4 ms 0.13 ms Unsampled 5
apps/projects/tests.py::ClassifyStreaksTest::test_test_changed_when_the_test_file_changed
passed 4 ms 0.49 ms 1 ms 2 ms Unsampled 5
apps/projects/tests.py::RealProfileDocumentTest::test_flat_stacks_still_work
passed 4 ms 0.55 ms 3 ms 0.12 ms Database 5
apps/projects/tests.py::ClassifyStreaksTest::test_environment_kinds_are_counted
passed 3 ms 0.53 ms 2 ms 0.12 ms Database 5
ft/tests.py::TestDatabaseConnectionRetries::test_gives_up_when_postgres_stays_down
passed 2 ms 0.43 ms 2 ms 0.10 ms Imports –
apps/projects/tests.py::ClassifyStreaksTest::test_test_changed_matches_paths_relative_to_the_repository
passed 2 ms 1 ms 1 ms 0.11 ms pytest 5
apps/guides/tests.py::TestContent::test_unknown_insights
passed 2 ms 0.49 ms 1 ms 0.37 ms Database 5
apps/projects/tests.py::ClassifyStreaksTest::test_ongoing
passed 2 ms 0.86 ms 0.96 ms 0.10 ms Database 5
apps/projects/tests.py::ClassifyStreaksTest::test_flaky_even_if_the_pass_came_first_and_elsewhere
passed 2 ms 0.48 ms 1 ms 0.11 ms Database 5
apps/projects/tests.py::SlugsAndNumbersTest::test_test_slugs_read_like_their_node_ids
passed 2 ms 0.67 ms 1 ms 0.09 ms Unsampled 5
apps/projects/tests.py::ClassifyStreaksTest::test_multiple_streaks_in_order
passed 2 ms 0.48 ms 1 ms 0.10 ms Database 5
apps/projects/tests.py::ClassifyStreaksTest::test_regression_caught_when_app_code_fixed_it
passed 2 ms 0.62 ms 0.97 ms 0.11 ms Database 5
apps/projects/tests.py::ClassifyStreaksTest::test_flaky_when_failed_and_passed_on_same_commit
passed 2 ms 0.67 ms 0.83 ms 0.10 ms Unsampled 5
apps/projects/tests.py::ClassifyStreaksTest::test_resolved_without_changed_files
passed 2 ms 0.45 ms 0.96 ms 0.12 ms Database 5
apps/projects/tests.py::ClassifyStreaksTest::test_no_failures
passed 1 ms 0.45 ms 0.91 ms 0.11 ms Libraries 5
ft/tests.py::TestDatabaseConnectionRetries::test_does_not_retry_other_errors
passed 1 ms 0.76 ms 0.60 ms 0.09 ms pytest –
ft/tests.py::TestDatabaseConnectionRetries::test_retries_while_postgres_restarts
passed 1 ms 0.45 ms 0.69 ms 0.09 ms Unsampled –
apps/projects/tests.py::MigrationInsightsTest::test_per_runner
passed 1 ms 0.94 ms 0.20 ms 0.08 ms Unsampled –
apps/projects/tests.py::MigrationInsightsTest::test_per_runner_needs_several_runners
passed 0.70 ms 0.50 ms 0.12 ms 0.08 ms pytest –
apps/projects/tests.py::MigrationInsightsTest::test_per_worker
passed 0.70 ms 0.47 ms 0.15 ms 0.07 ms pytest –
apps/projects/tests.py::MigrationInsightsTest::test_replace_insight
passed 0.68 ms 0.40 ms 0.13 ms 0.15 ms Unsampled –
apps/projects/tests.py::MigrationInsightsTest::test_per_worker_needs_repeated_builds
passed 0.65 ms 0.42 ms 0.13 ms 0.10 ms Unsampled –
apps/projects/tests.py::MigrationInsightsTest::test_per_worker_ignores_cheap_setups
passed 0.64 ms 0.44 ms 0.13 ms 0.07 ms Unsampled –
apps/projects/tests.py::MigrationInsightsTest::test_per_worker_tolerates_bad_fixture_data
passed 0.62 ms 0.43 ms 0.11 ms 0.08 ms Unsampled –

Slowest fixtures

Exact setup time across the session
Fixture Scope Calls Total Max
_django_setup_unittest class 55 2.04 s 2.03 s
django_db_setup session 1 2.02 s 2.02 s
_unittest_setUpClass_fixture_ProjectPagesTest class 1 245 ms 245 ms
_unittest_setUpClass_fixture_TestAccountSettings class 1 164 ms 164 ms
_unittest_setUpClass_fixture_AnalyticsTest class 1 155 ms 155 ms
_unittest_setUpClass_fixture_ProfilePagePaginationTest class 1 143 ms 143 ms
_unittest_setUpClass_fixture_McpTest class 1 140 ms 140 ms
_unittest_setUpClass_fixture_RealProfileDocumentTest class 1 121 ms 121 ms
_unittest_setUpClass_fixture_FlakyReportTest class 1 69 ms 69 ms
_unittest_setUpClass_fixture_MemoryTest class 1 68 ms 68 ms
_unittest_setUpClass_fixture_StorageTest class 1 64 ms 64 ms
_unittest_setUpClass_fixture_LegacyUrlTest class 1 48 ms 48 ms
_unittest_setUpClass_fixture_UnstorableCharactersTest class 1 40 ms 40 ms
_unittest_setUpClass_fixture_FlakyReportCacheTest class 1 37 ms 37 ms
_unittest_setUpClass_fixture_ProjectTestsPage class 1 24 ms 24 ms