0

DPWA: update doc about when to add integration tests

Change-Id: I340f02d852325a7cf3705c0f64f39822f0bdd50a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3457685
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Commit-Queue: Phillis Tang <phillis@chromium.org>
Cr-Commit-Position: refs/heads/main@{#970159}
This commit is contained in:
Phillis Tang
2022-02-11 21:59:58 +00:00
committed by Chromium LUCI CQ
parent ce0eb1782b
commit 55bb5e7063

@ -19,6 +19,10 @@ How-tos:
Related:
* [WebAppProvider README.md](/chrome/browser/web_applications/README.md)
## When to add integration tests?
A web app feature should have unit tests and browsertests that focus on testing the specific feature itself, the browsertests are capable of testing all the edgecases of the particular feature.
If a feature affects user-facing flows in any ways, integration tests should also be added to cover updates to web apps' critical user journeys. They wouldn't be as detailed as the browsertests that focus on all the way you can use the particular code component, but rather aim to cover the major ways users interact with the new feature.
## Future Work
* Allowing parameterized state-check actions.