Skip to content
#

test-runner

Here are 284 public repositories matching this topic...

jimmywarting
jimmywarting commented May 10, 2021
fd = new FormData
fd.set('a', new Blob)
fd.get('a') === fd.get('a') // false in chromium - true in FF & Safari (don't have IE on Mac)

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

ashwinvidiyala
ashwinvidiyala commented Feb 11, 2020

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

ward
MaxDesiatov
MaxDesiatov commented Jan 1, 2021

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.

mity
mity commented Jan 11, 2020

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:

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

Improve this page

Add a description, image, and links to the test-runner topic page so that developers can more easily learn about it.

Curate this topic

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."

Learn more