-
Updated
Feb 5, 2022 - JavaScript
test-runner
Here are 287 public repositories matching this topic...
-
Updated
Jan 2, 2022 - JavaScript
-
Updated
Jan 30, 2022 - JavaScript
-
Updated
Feb 5, 2022 - JavaScript
-
Updated
Feb 2, 2022 - 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:
Using HTTPS locally
Can we run the dev server over https?
I created locally signed ssl keys using mkcert, by following this guide: https://web.dev/how-to-use-local-https/
After setting up the cert and key files to my root directory, I added this to my dev server config:
...
sslKey: 'localhost-key.pem',
sslCert: 'localhost.pem',
};
I still cannot access my local ( localhost:8000 ) using
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
Jan 20, 2022 - Python
-
Updated
Sep 10, 2021
-
Updated
Feb 5, 2022 - C#
-
Updated
Jan 23, 2021
-
Updated
Feb 4, 2022 - C#
-
Updated
Dec 22, 2017 - JavaScript
-
Updated
Feb 11, 2021 - JavaScript
-
Updated
Apr 9, 2017 - JavaScript
-
Updated
Jan 27, 2022 - JavaScript
-
Updated
Feb 4, 2022 - Kotlin
-
Updated
Jan 20, 2022 - Python
-
Updated
Nov 15, 2021 - Python
-
Updated
Dec 10, 2021 - Java
From reading the docs, it does not appear possible to pass an extra -Xlinker flag when running carton bundle or carton dev
The SwiftWASM book which encourages users to install and Carton, does not mention it when it describes how to export a function: https://book.swiftwasm.org/examples/exporting-function.html
-
Updated
Jan 6, 2021 - Ruby
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
The green doesn't line up:
Other places, indentation increases either 2 or 4 spaces at a time:
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."



Relevant spec sections:
https://drafts.csswg.org/selectors-4/#the-dir-pseudo
https://html.spec.whatwg.org/multipage/semantics-other.html#selector-ltr
The interesting cases to test are from the definition of "directionality" in HTML:
https://html.spec.whatwg.org/multipage/dom.html#the-directionality
dir="ltr"matches:dir(ltr)(#26159)