chromium/src
0
Fork 0
Code Activity

Fix integration testing doc

Browse Source 
Replace the document linked in 'WebAppProvider/README.md' with
a new one. The original link to '/chrome/browser/web_applications/
README.md' now points to '/docs/webapps/README.md'.

Bug: None
Change-Id: I29698d620e944aef076822184580cbdcb88a8ab2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6505486
Commit-Queue: Euisang Lim <eui-sang.lim@samsung.com>
Reviewed-by: Euisang Lim <eui-sang.lim@samsung.com>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1455950}
This commit is contained in:
tomatozil
2025-05-05 14:42:49 -07:00
committed by Chromium LUCI CQ
parent 5205aaa8a3
commit f064a5ddce
2 changed files with 2 additions and 1 deletions

1
AUTHORS

@ -1633,6 +1633,7 @@ Yuki Tsuchiya <Yuki.Tsuchiya@sony.com>
Yuma Takai <tara20070827@gmail.com>
Yumikiyo Osanai <yumios.art@gmail.com>
Yumin Su <yuminsu.hi@gmail.com>
Yun Jiyun <tomatoziiilll@gmail.com>
Yunchao He <yunchao.he@intel.com>
Yupei Lin <yplam@yplam.com>
Yupei Wang <perryuwang@tencent.com>

2
docs/webapps/integration-testing-framework.md

@ -18,7 +18,7 @@ How-tos / guides:
* [Why is this test failing?][why-is-this-test-failing]
Related:
* [WebAppProvider README.md](/chrome/browser/web_applications/README.md)
* [WebAppProvider README.md](/docs/webapps/README.md)
## When to add integration tests?
Any web app feature (or any code in general) should have a combination of unit tests and browser tests that focus on testing the specific feature itself. Unit tests are the least likely to become flaky, and allow fine-grained testing of a system. Browser tests are more likely to be flaky but enable testing with most of the system running. Regular unit tests or browser tests should be used for testing system parts in isolation and for testing minute details like handling of error cases.