paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-11-04 05:53:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Add debugging tip for failure when typing on modal with puppeteer.

Browse Source
This commit is contained in:
Riken Shah
2021-03-29 20:51:15 +05:30
committed by Tim Abbott
parent e08bd9b1af
commit a2da736181
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/testing/testing-with-puppeteer.md
View File

@@ -82,6 +82,17 @@ integration](../testing/continuous-integration.md):
Integration (CI) services because small races are amplified in those Integration (CI) services because small races are amplified in those
environments; this often explains failures in CI that cannot be environments; this often explains failures in CI that cannot be
easily reproduced locally. easily reproduced locally.
* Does the test fail when you are typing (filling the form) on a modal
or other just-opened UI widget? Puppeteer starts typing after focusing on
the text field, sending keystrokes one after another. So, if
application code explicitly focuses the modal after it
appears/animates, this could cause the text field that Puppeteer is
trying to type into to lose focus, resulting in partially typed data.
The recommended fix for this is to wait until the modal is focused before
starting typing, like this:
```JavaScript
await page.waitForFunction(":focus").attr("id") === modal_id);
```
These tools/features are often useful when debugging: These tools/features are often useful when debugging: