Tell us about your environment:

• Puppeteer version: 1.14
• Platform / OS version: Windows
• Node.js version: 10

What steps will reproduce the problem?
try to pass a promise to await page.waitForResponse(response => condition) instead of urlOrPredicate.

What is the expected result?
expect async function to work

What happens instead?
no waiting as promise

Describe the bug
In the config.js addParameters function, if I set isFullscreen: true and open the webpage, it is fullscreen on startup. But if I set isFullscreen: false and open the webpage again, it is still full-screen on startup.

To Reproduce

1. Set isFullscreen: true, open the webpage,
2. Close the webpage or stop the server
3. Set isFullscreen: false, open the webpa

Given the immense popularity of Docker and the need to harden it different per platform (see ideas below) - we'd like to start writing a Docker best practices section.

You're welcome to contribute ideas and write best practices - writing and brainstorming will people is an amazing way to deepen your Docker understanding.

At first, we want to collect ideas for best practices, solidify a list

Current behavior:

We use --env variable to pass some environment variables to cypress, when it's running both in headless and headed mode.

One of the parameters is a hash (mix of numbers and characters). Surprisingly some specific hash values make cypress to fail reading this value from the command line (e.g. 769e98018). The corresponding environment variable is not set and the `Cyp

I'm getting bit with failing documentation builds because I'm writing docstrings that JSDoc doesn't like (specifically, TS-style). But there's no linting happening before getting to Netlify.

We may be able to make JSDoc just check the syntax and exit (and make it part of the lint scripts).

This is moot if we want to move forward with maintaining our own TS types (for which there is an op

Spurred by conversation in avajs/ava#2449 and avajs/ava#1485 we'd like for our assertions to return booleans. true when they pass, false when they fail. This does not apply to the throws() and throwsAsync() assertions.

Failing assertions will fail the test, but do not throw exceptions. This means your test does not stop executing. Usua

Is your feature request related to a problem? Please describe.
This is releated to this.

I believe documentation on the topic of mocking is outdated. I'm quite new to React Native and it took me a while until I figured that current version of metro does not support `r