test-runner

To reproduce:

1. Open Cypress.
2. Click “View App Data” via the context menu.
3. App crashes.

Desired behavior: View App Data works, and errors with View App Data are gracefully handled.

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

• element with dir="ltr" matches :dir(ltr) (#26159)
• root element without `

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

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

The default output doesn't have much contrast and is a bit hard to read for me. That's best illustrated with a screenshot:

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.

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

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:

0. Explore what API is available for the purpose on the platform of your choice.
1. A pre-pro