testing-library-docs
testing-library-docs copied to clipboard
docs site for @testing-library/*
> Spectacular documentation now has a page on Angular Testing Library integration which is the recommended developer experience for feature testing... > https://ngworker.github.io/ngworker/docs/feature-testing/angular-testing-library/ https://twitter.com/LayZeeDK/status/1441016955692064772
continue from #930 I added [React Testing Library React Dnd Chessboard Example](https://github.com/laststance/react-testing-library-react-dnd-chessboard-example) at the `example-external` page. Thanks!
### Why? I am so upset for can't open the [document site](https://testing-library.com/), I don't know why. Maybe I come from China. ### Affect I can read nothing by the document....
I really like the change to recommend msw as the way to mock api requests however with nextjs there are some conventions that nextjs picks up on to make things...
**Is your feature request related to a problem? Please describe.** I was talking to some brazilian people who wanted to learn more about the Testing Library but the were struggling...
Previous version of this file what seemed to use an older syntax of `testing-library`. It involved direct DOM manipulation and use of ReactDOM. I corrected it to what I believe...
*docs: update example-react-route.mdx *docs: replace createMemoryHistory with MemoryRouter for first test-case Fix #897
It is generally recommended to make queries via the screen object. This PR updates some examples on the "Appearance and Disappearance" page to stick to that best practice.
# Change * Update Keyboard events example code to include ```charCode``` in the event properties object - this update relates to [issue 269](https://github.com/testing-library/react-testing-library/issues/269)
Starting point: summarize discussion at https://github.com/testing-library/testing-library-docs/issues/738