![\"Open](\"/assets/images/award-4ab55893b6382919b43dff3db505287a.jpg\")
Hello friends! I'm pleased to announce the recent updates to the testing-library\nfamily of tools! As always, we're committed to giving you the best tools to\nenable you to have confidence in shipping your applications. That's why the\nguiding principle for everything we do is:
The more your tests resemble the way your software is used, the more confidence they can give you.
This guiding principle has given us direction and we've been able to accomplish\na lot in the testing space. To further our mission, I'd like to make a few\nannouncements about changes going on in the testing-library world.
This is actually a pretty small release, but I think it's worth mentioning\nanyway. We try to keep breaking changes to a minimum. This release only has two\nbreaking changes. One is removal of deprecated methods you probably weren't\nusing anyway, and the other reveals potential bugs in your tests. So you should\nbe able to upgrade to this version with little-to-no effort.
If you do experience breakages, it's probably due to something like this:
We hope that this helps you catch bugs better!
react-testing-library\nand\ncypress-testing-library\nhave already been updated and released major version bumps of their own to\naccount for this upgrade. Other wrappers will hopefully follow shortly based on\ntheir respective matinainers' schedules.
We've created a new org on GitHub to manage the family of testing library\nprojects. The best part of the \"Testing Library\" isn't the code, but the\nphilosophy behind it. So we're using the organization as a way to group all the\nprojects that share the same philosophy and general utilities so whether you're\nusing Vue, Cypress, or React (Native), you'll have a super testing tool that\nyou're familiar with.
Here are the current (or soon to be) members of the org:
(Hopefully we'll have\nangular on there eventually\nas well as ember).
What's cool is that building wrappers for your JavaScript framework of choice is\noften quite simple (as I demonstrate on\nTestingJavaScript.com). And as mentioned below,\nyou can carry these same principles to non-DOM platforms as well!
If the Testing Library family of tools has provided you any value at all, we'd\nencourage you (or your employer) to contribute to our new\nOpen Collective.
It is intended that funds raised by this open collective be used to:
There are currently no plans to pay people who work on the project, but we\nreserve the right to do so if it makes sense in the future.
A lot of chatter is going on in the Testing Library world on Twitter, so we've\ncreated a twitter account you can follow and keep up with what's going on.
We've had a pretty active spectrum community for react-testing-library. We're in\nthe process of moving that to a more general Testing Library spectrum so we can\nhave all discussion around the different wrappers in one place. There are over\n600 members of our spectrum community (special shout-out to\nGiorgio who has been SUPER helpful to people\nthere.) Please join us!
I'm really happy to announce a super solution to the React Native testing space.\nThe DOM is quite different from native, as I mentioned before, it's not the code\nbut the concepts that really make the Testing Library great. I'm happy to say\nthat Brandon Carroll has successfully ported\nthose concepts to a solution for React Native and I'm really happy with it. Give\nit a look if you're building React Native applications and want confidence that\nthey continue to work as you make changes!
There's been a LOT of activity around the Testing Library principles and tools\nin the content space. We do have\na page that lists learning materials, and more gets added to\nit daily. If you know of blog posts, YouTube videos, courses, or anything else\nabout the Testing Library family of tools, please contribute to the list!
As of a few months ago,\nthe React team officially recommends\nyou use react-testing-library to test your react applications. That's kinda neat\n:)
At the React Amsterdam Open Source awards\nceremony, react-testing-library won the award for the Most impactful\ncontribution to the community!
react-testing-library also received recognition on the\nThoughtWorks Technology Radar\nas technology they believe is \"Worth exploring with the goal of understanding\nhow it will affect your enterprise.\" We think so too :)
Each of the projects has had many contributors and on most projects in\nthe org, you'll find a table of\ncontributors. We're super grateful for all the contributions people have made to\nthe projects. I'd like to also give a special shout-out to people who have made\nan especially significant impact on the Testing Library family of tools and\ncommunity.
Myself 👋, Alex Krolick,\nBrandon Carroll,\nGiorgio,\nErnesto García, and\nDaniel Cook.
As I said, there have been many who have contributed a great deal to the\ncommunity, but these people stand out to me as individuals who have done\nespecially great work. Thank you!
No matter what platform you're working with, the guiding principles of the\nTesting Library family can be applied to the tests for that platform. Take a\nstep back and consider how closely your tests are resembling the way your\nsoftware is used. If you can, consider what lightweight but powerful utilities\nwould enable others to test their software in that way as well and create a\nlibrary for that! Maybe it can join the Testing Library family of tools!
", "url": "https://testing-library.com/blog/2019/04/25/new-org", "title": "Testing Library Updates: new release, github org, open collective, and twitter account", "summary": "Hello friends! I'm pleased to announce the recent updates to the testing-library", "date_modified": "2019-04-25T00:00:00.000Z", "author": { "name": "Kent C. Dodds", "url": "https://kentcdodds.com" }, "tags": [] }, { "id": "/2019/03/17/code-blocks", "content_html": "Many of the code samples have been updated to include tabs to switch between\n\"plain\" DOM Testing Library syntax and the wrappers for React, Cypress, etc.
Thanks to @tylerthehaas for pointing out that\nthe previous examples could be confusing if you were targeting a specific\nlibrary, and to the Docusaurus team for adding support for code tabs in version\n1.7.2.
", "url": "https://testing-library.com/blog/2019/03/17/code-blocks", "title": "Multi-Framework Code Blocks", "summary": "Many of the code samples have been updated to include tabs to switch between", "date_modified": "2019-03-17T00:00:00.000Z", "author": { "name": "Alex Krolick", "url": "http://github.com/alexkrolick" }, "tags": [] }, { "id": "/2018/12/29/new-site", "content_html": "We have a docs site now! It's built with Docusaurus.
The new site is the homepage for DOM Testing Library, React Testing Library, and\nthe *-testing-library ecosystem. Check out the landing pages for each:
💯 Thank you to everyone who has contributed to the docs over the past months -\nthe content has been ported over and the hope is that this site will provide a\ncentralized place for examples, API reference, and community links in 2019 and\nbeyond!
🎉 Happy new year!
", "url": "https://testing-library.com/blog/2018/12/29/new-site", "title": "New Site", "summary": "We have a docs site now! It's built with Docusaurus.", "date_modified": "2018-12-29T00:00:00.000Z", "author": { "name": "Alex Krolick", "url": "http://github.com/alexkrolick" }, "tags": [] } ] }