You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tests always seem to fail whenever I use modern keywords like const?
Or is this because setup/teardown and test-code isn't all defined/running in the same scope? (if so, how is teardown useful without being able to access any of the results generated by the tests?)
(I'd assume every test runs in a new iframe with setup, test-code and teardown "pasted" after each other, or how else does it work? how else would you get reliable results?)
It would be helpful if you could console.error after you catch, as currently there's no way to see which line generated the error.
Also, the preparation code rendering is broken, with two weird nested containers and some <script> tags showing up on the page - I have no idea if this is related.
The text was updated successfully, but these errors were encountered:
This test fails with a cryptic error message:
https://jsperf.com/array-search-sets
Tests always seem to fail whenever I use modern keywords like
const
?Or is this because setup/teardown and test-code isn't all defined/running in the same scope? (if so, how is teardown useful without being able to access any of the results generated by the tests?)
(I'd assume every test runs in a new iframe with setup, test-code and teardown "pasted" after each other, or how else does it work? how else would you get reliable results?)
It would be helpful if you could
console.error
after youcatch
, as currently there's no way to see which line generated the error.Also, the preparation code rendering is broken, with two weird nested containers and some
<script>
tags showing up on the page - I have no idea if this is related.The text was updated successfully, but these errors were encountered: