react-testing-library VS react-testing-library

I'm currently testing an input using Jest & react-testing-library. I'm trying to test whether the onChange function fires whenever my input's field changes. Here's an example of my code:

I am trying to test the onChange event of a Select component using react-testing-library.

Reactjs Current Working Solution Using this html: Name: Bob (special guest) I can use the React Testing Library getByTestId method to find the textContent: expect(getByTestId('foo').textContent).toEqual('Name: Bob (special guest)') Is there a better way? I would like to simply use this html: Name: Bob (special guest) And use React Testing Library's getByText method like this: expect(getByText('Name: Bob (special guest)')).toBeTruthy() But this does not work. So, the question… Is there a simpler way to use React Testing Library to find strings of text content with the tags striped out? Answer link : https://codehunter.cc/a/reactjs/how-to-query-by-text-string-which-contains-html-tags-using-react-testing-library

I am new to react-testing-library / jest and attempting to write a test to see if the navigation of routes (using react-router-dom) is performed correctly. So far I have been following the README and this tutorial on how to use.

I'm using react-testing-libarary to test my react application. For some reason, I need to be able to find the element by id and not data-testid. There is no way to achieve this in the documentation.

React Testing Library

After searching for a workaround, I found this issue thread on the React-testing-library Github page, which gave me a clear solution.

yeeeesss and as an advice use testID in most of matcher cases. also do not rely only on detox matcher try https://github.com/testing-library/react-testing-library

React Testing Library: This library provides simple and complete React DOM testing utilities that encourage good testing practices. It helps you write tests that are more focused on the behavior of your components rather than the implementation details. https://github.com/testing-library/react-testing-library

I've had a number of issues since the upgrate to React 18, notably this one.

For more information see: - The PR implementing 'renderHook' in React Testing Library

Really? It seems like it's already been replaced. Can you link to where it's not quite deprecated yet? https://github.com/testing-library/react-testing-library/releases/tag/v13.1.0

expect(wrapper.find('FetchNextPageButton').props()).toMatchObject({ query: NEWS\_QUERY, path: "viewer.news"}) So I'm wondering what's the best approach to test it by using React testing library instead.

^ jest for running the tests & @types/jest to help with IDE auto-complete when writing tests. @testing-library/react to render components in the testing environment & test them in a way that tries to mimic how users interact with them. @testing-library/jest-dom for additional DOM-related assertions.

There are many ways to test component UIs and some testing frameworks help us achieve that, to mention but a few react-testing-library, where we write tests to check what a component has, for example, if we are testing a form component, we will write tests to check it a button is rendered, if there are input and/or select tags, etc and we usually see the results in our terminals but with React cosmos, we have a visual way to test our components (Visual TDD) which makes testing easier.