We should test that about:crash and about:inducebrowsercrashforrealz always generate crash reports in Chrome. Visit one of these URLs and run crashpad_database_util (https://crashpad.chromium.org/man/crashpad_database_util.html) to inspect the state of the database.

We should test that these crash reports are not uploaded anywhere in Chromium builds, or in Chrome builds with the upload pref turned off.

We should test that these crash reports are uploaded in Chrome builds with the upload pref turned on. This testing should redirect the upload to a test server running on localhost, so that we don’t spam the real crash server with test crashes.

Because tests do run nearly as often in officially-branded Chrome builds as in Chromium builds, perhaps we should have a permutation that forces the upload on even when testing in Chromium, to ensure that uploads are functioning and that regressions are caught rapidly.

If we retain any form of client-side rate-limiting, we may also want to test that it behaves properly.