-
Updated
Apr 16, 2020 - JavaScript
wallaby
Here are 36 public repositories matching this topic...
Issue description or question
The coverage markers usually remain green for the lines that contain the test declaration in Jest. This is usually not a problem until those tests are collapsed (folded). When the tests are folded, then it becomes more difficult to tell that the tests did not run just by scanning the coverage markers.
For example:
![image](https://user-images.githubuserc
-
Updated
Nov 11, 2018 - TypeScript
Update dependencies
Currently new Babel supports typescript. Use it.
Also update security and deprecation varnings.
- Use babel
- Update dependencies
- Fix security issues
- Fix CI
-
Updated
Jul 15, 2018 - TypeScript
-
Updated
Oct 24, 2018 - JavaScript
-
Updated
May 5, 2017 - TypeScript
-
Updated
Apr 18, 2018 - JavaScript
-
Updated
May 3, 2020 - JavaScript
-
Updated
Mar 14, 2020 - JavaScript
-
Updated
Jan 22, 2019 - JavaScript
-
Updated
May 11, 2020 - JavaScript
-
Updated
Jun 6, 2020 - TypeScript
-
Updated
Mar 15, 2020 - TypeScript
-
Updated
Jun 6, 2017 - JavaScript
Improve this page
Add a description, image, and links to the wallaby topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the wallaby topic, visit your repo's landing page and select "manage topics."
I propose that we should remove the ability to pass an element to any of the
Browserfunctions. Doing this removes an entire class of race conditions since queries block until they become true. This also makes the api more consistent and should help to reduce issues with chaining. We already supportElementso if people want to find a specific element and then pass that element to the `Element