The more your tests resemble the way your software is used, the more confidence they can give you.
We try to only expose methods and utilities that encourage you to write tests that closely resemble how your apps are used.
Utilities are included in this project based on the following guiding principles:
- If it relates to rendering components, it deals with native views rather than component instances, nor should it encourage dealing with component instances.
- It should be generally useful for testing the application components in the way the user would use it. We are making some trade-offs here because we're using a computer and often a simulated environment, but in general, utilities should encourage tests that use the components the way they're intended to be used.
- Utility implementations and APIs should be simple and flexible.
In summary, we believe in the principles of testing-library
, and adhere to them as closely as
possible. At the end of the day, what we want is for this library to be pretty light-weight, simple,
and understandable.
Thanks goes to these wonderful people (emoji key):
Brandon Carroll π» π π π¨ |
Jean-Marie Porchet π |
Santi π |
Ely Alvarado π |
Javier Alvarez π |
Matt Wood π |
Jeremy Davis π |
MoeSauber π |
Hans Hoffman π |
Luca Barone π |
Louis H π |
This project follows the all-contributors specification. Contributions of any kind welcome!