react-beautiful-dnd VS react-testing-library

Yeah, I hope the migration is not going to be too painful because https://github.com/atlassian/react-beautiful-dnd is a key component in one of my important project

For this full-stack single-page app, you'll use Vite.js as your frontend build tool and the react-beautiful-dnd package for draggable items.

A huge win for the user experience using react-beautiful-dnd.

react-beautiful-dnd stands out as the most commonly used, it provides a clean and high-level API with a lot of abstraction. It was developed by Atlassian.

Drag-and-drop library for React with beautiful animations. Website - GitHub

This library is very cool and pretty simple to use : https://github.com/atlassian/react-beautiful-dnd

Not sure if OP used these but here are few suggestions: For drag drop: https://www.npmjs.com/package/react-beautiful-dnd For resizing with handles: https://www.npmjs.com/package/react-resizable

https://github.com/react-dnd/react-dnd https://github.com/atlassian/react-beautiful-dnd

You can try react-beautiful-dnd, it's amazingly simple, I actually switched from react-dnd a couple months ago to react-beautiful-dnd, and it was easy af.

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.