#reacttestinglibrary risultati di ricerca
React Testing Library waitFor not working with setTimeout stackoverflow.com/questions/6597… #reactjs #reacttestinglibrary
.@kentcdodds I love the new `rerender`, `unmount`, and `result` return values from `testHook` in #ReactTestingLibrary. 🐐
Continuing our series from last week, Charan lead us through Part-II of Automated Test. We discussed - ✅Mock testing (mock responses) 🪝testing approach for custom hooks 🃏Faker library #AutomatedTest #React #ReactTestingLibrary #ProximityTechWeekly #ProximityWorks #proxonauts
My journey with #reactTestingLibrary began. If you want to be a javascript ninja 👉@kentcdodds === OBI-WAN KENOBI ⚔️ “Use the react-testing-library, Luke.” is the new Jedi moto ...
Been using this custom testing-library/react renderer for a few months now and it has made it significantly easier to write tests by logging fragment diffs for better feedback while testing. Gist: gist.github.com/tannerlinsley/… #testinglibrary #reacttestinglibrary
Day 78 #100DaysOfCode - Spent some time playing with React app coverage using #Jest and #ReactTestingLibrary. Also found out Istanbul coverage tool comes pre-packaged in Jest 🤔 🤩 - Also spent some time adding IE styles support for work/ rediscovering IE devTools:
Writing tests that use shallow rendering came up at work today (I'm not a fan). It prompted me to say this. In other words, test the behavior of a component, not the implementation. That's why I use @kentcdodds' #ReactTestingLibrary to test components.
How to test a function inside React functional component using jest.spyOn with React Testing Library stackoverflow.com/questions/6806… #jestjs #reactjs #reacttestinglibrary #javascript
#ReactTestingLibrary has made testing so easy that even I can write some tests here and there now. Thank you very much, @kentcdodds for all of your awesome OSS projects.
A really great talk @ReactLoop by @elizfunk that I think did #ReactTestingLibrary justice and hit on some of the key points for using it. I think @kentcdodds would have loved the talk!
Need to spice up that weekly standup and get support for your push to use 🐐 #ReactTestingLibrary? For a small fee, this farm will have a goat join your @zoom_us call. facebook.com/57296698983042…
Getting the hang of #ReactTestingLibrary. Still have work to do in this component, but I better call it a night 🛌💤 Definitely lost track of time, but that's what happens what you get into the flow state.
queryByRole, queryByText fixed the “overlapping act() calls” warning I was getting in #reacttestinglibrary and #jest, and I wasn’t using act() 😬😬🤔 #React #javascript #DEVCommunity #SoftwareEngineer
I am now officially a contributor to @kentcdodds' #ReactTestingLibrary. 🐐 Check out the new `testHook` utility that I wrote for testing React custom hooks. Thx Kent! Ship your custom hooks with confidence! 💪 #reactjs #hooks #testing github.com/kentcdodds/rea…
#React Testing Library: The Modern Way to Test React Components bit.ly/2LFCGtl #ReactTestingLibrary #JavaScript #WebDevelopment
#ReactTestingLibrary TIL I ran into an issue testing a component that uses a Portal downstream. The preferred solution I found, per @kentcdodds, was to add a couple lines to the base Portal component to ensure its root element is on the DOM. github.com/jbranchaud/til…
Day 89 of #100DaysOfCode #ReactTestingLibrary ✅ userEvent.hover and unhover for mouseover events ✅ queryByText() and expect().not.toBeInTheDocument() for element starts out not in the page ✅ async waitForElementToBeRemoved for element that was there and disappeared #ReactJS
📢@danieljcafonso favourite #React libraries are... "#ReactTestingLibrary - testing is important & I like to sleep well at night. And #ReactQuery. If you've to deal with data fetching, you'll be aware it's very tricky. React Query has made it so easy" ➡reactadvanced.com
"How to use React Testing Library to rewrite an Enzyme Component test: a mini-rewrite case study of two testing libraries" check out the latest on react-testing-library from engineer @lukeghenco buff.ly/2RPTf7z #reactjs #reacttestinglibrary
🚨 The #React RCE Nightmare: Why #CVE-2025-55182 Is Your Wake-Up Call and How to Scan Your 55 Million Potential Targets undercodetesting.com/the-react-rce-… Educational Purposes!
🚨 React2Shell: The Catastrophic Unauthenticated RCE Vulnerability Haunting Every #React App undercodetesting.com/react2shell-th… Educational Purposes!
📛 react 🧠 React is a versatile JavaScript library for creating interactive, component-based user interfaces, easily integrated into current projects. 🛠️ @MetaOpenSource 💻 JavaScript ⭐ 241297 🍴 50018 🔗 github.com/facebook/react
Check out the React test server for testing React2Shell vulnerabilities.
We've open-sourced a React test server for demonstrating and testing the React2Shell vulnerability (CVE-2025-55182).
📛 react 🧠 React is a versatile JavaScript library for creating interactive, component-based user interfaces, easily integrated into current projects. 🛠️ @MetaOpenSource 💻 JavaScript ⭐ 241177 🍴 50009 🔗 github.com/facebook/react
🚨 React2Shell: How a Single #React App Vulnerability Unleashes Total Server Compromise (#CVE-2025-55182 Deep Dive) undercodetesting.com/react2shell-ho… Educational Purposes!
📌 The library for web and native user interfaces. 🔹 1. **Composants réutilisables** 🔹 2. **Virtual DOM performant** 🔗 github.com/facebook/react #JavaScript
🖥️ #React Server Components Exposed: The Silent RCE Storm Crippling Modern Web Apps undercodetesting.com/react-server-c… Educational Purposes!
Built a vulnerable React/Next.js lab for testing the #React2Shell bugs (CVE-2025-55182 & CVE-2025-66478). Everything ships in Docker containers.. use it 4fun github.com/jctommasi/reac…
🚨 React2shell: The 10/10 RCE That Turns Your #React App into a Remote Shell (#CVE-2025-55182 / #CVE-2025-66478) undercodetesting.com/react2shell-th… Educational Purposes!
Playwright + React = Faster, cleaner, more reliable testing. From cross-browser support to detailed reporting, it’s everything modern teams need. Read: testrigtechnologies.com/integrating-pl… #React #Playwright #QA #softwaretesting
Here is a list of nine React testing best practices for better design and quality of your tests: 1. Favor Arrange-Act-Assert (AAA) pattern 2. Avoid testing too many things at once 3. Be careful with snapshot tests 4. Test the Happy Path first 5. Test Edge Cases and Errors…
LOL upgrading @testing-library/react made it WORSE somehow how is this happening fuck this absolute fucking shit
Write maintainable tests for your Svelte components with the lightweight DOM testing utilities provided by svelte-testing-library 🧪 - madewithsvelte.com/svelte-testing…
My react components are tested. I just create tests for backend and frontend by using vitest framework.
Something went wrong.
Something went wrong.
United States Trends
- 1. #UFC323 128K posts
- 2. Merab 47.2K posts
- 3. Indiana 107K posts
- 4. Petr Yan 28.3K posts
- 5. Roach 29.3K posts
- 6. Duke 61.4K posts
- 7. SB19 ACONic PERFORMANCE 93.3K posts
- 8. Ohio State 64.7K posts
- 9. Good Sunday 50.8K posts
- 10. Mendoza 42.3K posts
- 11. Pantoja 35.8K posts
- 12. Benin 36K posts
- 13. TOP CALL 8,867 posts
- 14. Walt 8,348 posts
- 15. Joshua Van 11.4K posts
- 16. Heisman 19.6K posts
- 17. Curt Cignetti 12K posts
- 18. Manny Diaz 3,026 posts
- 19. Vtubers 5,782 posts
- 20. Tulane 18K posts