Rick Waldron
Rick Waldron
@ljharb since it's not a normally specified mechanism with an exposed API surface, it could very well be all of them. Out of all of the engines I've written support...
@ljharb tests regularly "monkey patch" parts of built-ins to catch specific observable behaviors occurring. A really good example of where that happens is in the Promise tests.
@ptomato I have to respectfully disagree with your claim in the original post. Here are 5 tests that exercise step 1, 2, 3 and 4; where 4 is tested two...
@ptomato then I guess I'm saying: given all specs I've read, with the exception of WeakMap and FinalizationRegistry, there is no specification that cannot have its steps tested in sequence...
@ljharb > I frequently do this sort of thing in tests, and test/mocking frameworks all tend to have an "after" or "cleanup" mechanism to queue up the restoration code. Yes,...
@ptomato (Quick tone check on myself: I want to make sure you know I'm replying in good faith and by no means intend for any of this to be interpreted...
With regard to the skiplists I provided: imagine if each of those listed files contained tests that were trying to test a bunch of steps in an algorithm, where maybe...
Both @leobalter and I are on vacation this week. I will look at this first thing next week.
Nice! Let's do it
@jugglinmike I like this solution.