pptr-testing-library icon indicating copy to clipboard operation
pptr-testing-library copied to clipboard

puppeteer + dom-testing-library = 💖

Results 26 pptr-testing-library issues
Sort by recently updated
recently updated
newest added

while technically not part of `dom-testing-library` it'd be nice to offer the same convenience expectations. Maybe this belongs in [jest-puppeteer](https://github.com/smooth-code/jest-puppeteer)? ```js import 'dom-testing-library/extend-expect' // Hello World expect(queryByTestId(container, 'greetings')).toBeInTheDOM() expect(queryByTestId(container, 'greetings')).not.toHaveTextContent('Bye...

parity

### Description First: a disclaimer that I am not sure at all where this issue originates but am asking here to see if anyone has any thoughts on where to...

It looks like puppeteer is up to major version 7, but pptr-testing-library still checks for v1 or v2 in peerDependencies. Would it be possible to bump that?

Following [this](https://github.com/testing-library/dom-testing-library/pull/809#issue-515554670) PR by @kentcdodds, we're migrating all travis pipelines to github actions :) An example for the action can be seen [here](https://github.com/testing-library/dom-testing-library/blob/master/.github/workflows/validate.yml).

`waitFor` and `find*` queries are supported but `waitForElementToBeRemoved` is not currently. It would be useful to add this async util to avoid having to write boilerplate code around `waitFor` and...

enhancement

Current, the `extend` tries to require and modify the `puppeteer` module. However, I've found several use cases for using `puppeteer-core` to already-installed browsers and not require users to install an...

enhancement

There a few env vars that affect dom-testing-library that would be helpful to pass/inject into the pttr DOM. For now it looks like `DEBUG_PRINT_LIMIT` is the only one.

enhancement

right now the entire dom-testing-library is sent on each evaluateAsync call to avoid execution context change problems (and global pollution), instead it could be installed just once on each page...

perf

In https://github.com/puppeteer/puppeteer/pull/8844, which was released as part of Puppeteer v17, the execution context has been marked internal, so this access is no longer possible. I see it's being used twice...

update to support `.frame` instead of `.executionContext`