Glic API tests fail even if the assert error was captured Update the API test harness to track test assertion failures and force tests to fail even if the assertion error was captured by the test. Add tests to confirm that all current assertion helpers are supported. Additionally, add a text message argument to most assert-like helpers, include error message checking in `assertRejects`, and standardize failure error messages. Bug: b:434762167 Change-Id: I762caa7080e0ce502b861eb74a3d158c0476ceea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6795487 Reviewed-by: Dan Harrington <harringtond@chromium.org> Auto-Submit: Carlos Knippschild <carlosk@chromium.org> Commit-Queue: Carlos Knippschild <carlosk@chromium.org> Cr-Commit-Position: refs/heads/main@{#1494265}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.