Steve Gravrock
Steve Gravrock
This is more interesting (read: harder) than I thought it was going to be. I expected that the major sources of overhead would be the recursive calls to `MatchersUtil#eq_` and...
I'm glad the workaround worked for you. > I understand the issue with devs maybe defining custom properties on their typed arrays, but they should be the ones requiring custom...
PhantomJS is not supported. Its last release was in 2016 and development ceased in 2018. We haven't been able to test Jasmine against it since version 3.4 (almost three years...
See #1966. The popular state management framework mobx adds non-numeric properties to arrays. This suggests that it's actually fairly common for arrays to have extra properties. Not only that, but...
It would be interesting to know more about your testing strategy, particularly what the code in the `// skip these steps as they are not relevant in this case` branch...
Apologies in advance if I've misunderstood what you're doing or am about to get some math wrong. It sounds like you care about testing both the A path and the...
Sounds good to me.
This would be pretty difficult to solve in 2.x, but it seems like it should be easy enough once #1409 is implemented.
I can definitely see the value of that. Jasmine's own test suite solves the same problem by booting two completely independent copies of Jasmine. But that's not a particularly easy...
On the one hand, we don't support configurations where Jasmine itself or the JS runtime has been monkey-patched. And as far as I know the Angular folks have generally seen...