-
Updated
Aug 16, 2021 - JavaScript
test-runner
Here are 284 public repositories matching this topic...
-
Updated
Aug 13, 2021 - JavaScript
-
Updated
Aug 13, 2021 - JavaScript
-
Updated
Jun 28, 2021 - JavaScript
-
Updated
Aug 14, 2021 - JavaScript
For the longest time I was able to access the pry console while running tests using :TestNearest, but it hasn't been working of late. I am able to run tests using :TestNearest and the other vim-test commands. My issue is that if I throw in a binding.pry in the test, I don't see the pry console open up anymore in the test window. That used to work before, and I can't figure out why. I'm
Jest on windows
The default output doesn't have much contrast and is a bit hard to read for me. That's best illustrated with a screenshot:
wds not found
The lit documentation suggest to use this server for development, so I created an empty project / directory.
Initialized it with npm init and installed the server using npm i --save-dev @web/dev-server.
However according to the documentation (https://modern-web.dev/docs/dev-server/overview/) I should be able to start the server with web-dev-server --node-resolve --open or `wds --node-resol
-
Updated
Jul 24, 2021 - Python
-
Updated
Aug 11, 2021
We need a page in the docs that tell users that to mock they should use from unittest import mock.
We should note that the mock.patch decorators don't currently work, and that we need to use the context managers instead.
-
Updated
Aug 16, 2021 - C#
-
Updated
Jan 23, 2021
-
Updated
Aug 14, 2021 - C#
-
Updated
Dec 22, 2017 - JavaScript
-
Updated
Feb 11, 2021 - JavaScript
-
Updated
Apr 9, 2017 - JavaScript
-
Updated
Aug 1, 2021 - JavaScript
-
Updated
Aug 14, 2021 - Kotlin
-
Updated
Aug 5, 2021 - Python
-
Updated
Jun 9, 2021 - Python
-
Updated
Mar 28, 2021 - Java
-
Updated
Jan 6, 2021 - Ruby
In addition to defaultBrowser we should add chrome, safari, firefox, and edge as possible arguments passed to carton test --environment. This would allow testing with an arbitrary browser, not just default browser. carton test should check if a given browser is available before attempting to launch it, and display an appropriate error message if a given browser is absent.
Make the output, especially as generated by the macros TEST_CHECK(), TEST_MSG() and TEST_DUMP(), automatically adapt to the current terminal size, so that it looks good in a reasonably small terminal window but can use effectively more space if the terminal window is big.
This should involve:
- Explore what API is available for the purpose on the platform of your choice.
- A pre-pro
This looks to be something legacy which hasn't been updated in several releases. I've asked Charlie Poole/Rob Prouse if they can remove it from the choco site, as maintainers. We should also remove the packaging from the repo here.
https://www.chocolatey.org/packages/nunit-console-with-extensions
Consider the below test case, the language is Icelandic.
The test explorer shows this test case as
Notice that \u0081 is being added in between two characters as a
Improve this page
Add a description, image, and links to the test-runner topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the test-runner topic, visit your repo's landing page and select "manage topics."



Looks like there is no test to cover this senario: https://github.com/web-platform-tests/wpt/blob/e45a9f9e65d039c76817ee2a6a1ef02c9311a1cb/xhr/formdata/set-blob.any.js
I think
fd.get('a') === fd.get('a')should be true