em
dom-testing-library
| em | dom-testing-library | |
|---|---|---|
| 2 | 4 | |
| 251 | 3,232 | |
| 0.8% | 0.5% | |
| 9.8 | 6.5 | |
| 3 days ago | 13 days ago | |
| TypeScript | JavaScript | |
| GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
em
-
Problems with using `useFakeTimers('modern')` in a create-react-app (CRA) project with Jest 26 and Lodash's `debounce` function
I kept looking through Github issues and PRs to try and work out what my local application was missing, and why the documentation examples didn't work for me. Eventually, I found this issue and its associated pull request where a contribitor discovered why their use of jest.useFakeTimers('modern') was failing:
-
But really, come on now
[em](https://github.com/cybersemics/em)
dom-testing-library
- Buenas prácticas con Angular Testing Library
-
Problems with using `useFakeTimers('modern')` in a create-react-app (CRA) project with Jest 26 and Lodash's `debounce` function
I did some digging and it looks like testing-library/dom-testing-library recommended using jest-environment-jsdom-sixteen in its release notes for v7.0.0 because CRA was using an older version of Jest which provided an older version of jsdom that was missing support for things like MutationObservers and other modern web features. However, eventually CRA was updated to use the newer version of Jest, and this made using jest-environment-jsdom-sixteen unnecessary – and in this case actually harmful as it prevented me from using the new useFakeTimers('modern') functionality. Once I removed the --env=jsdom-sixteen line from the test script in package.json everything started working as I expected.
-
How to test a select element with React Testing Library
"xByRole" is the most "correct" one, but it is also really slow if you're rendering something complex. Just a heads up. See this github issue for more info.
-
Using RTL: getByRole is quite slow on simple tests
https://github.com/testing-library/dom-testing-library/issues/820#issuecomment-726936225
What are some alternatives?
dendron - The personal knowledge management (PKM) tool that grows as you do!
atl-good-testing-practices
github-orgmode-tests - This is a test project where you can explore how github interprets Org-mode files
jest - Delightful JavaScript Testing.
logseq13-full-house-plugin - Logseq Templates you will really love ❤️ 🏛️
mindforger - Thinking notebook and Markdown editor with LLM wingman.
ayu - 🎨🖌 Modern Sublime Text theme
athens - Athens is a knowledge graph for research and notetaking. Athens is open-source, private, extensible, and community-driven.
veaos - Veaos is a free open source Q&A and knowledge management platform
foam - A personal knowledge management and sharing system for VSCode
thinktool - Novel fusion of hierarchical and graph-based approaches to taking notes, based on ideas from Roam Research, TheBrain and others.