3 ms·
Thanks so much to the PhantomJS maintainer for his hard work over the years! To me, it feels like his decision is the correct one here. After we realised that
by moogly 10y ago
Thanks so much to the PhantomJS maintainer for his hard work over the years! To me, it feels like his decision is the correct one here.
After we realised that we hadn't seen a "one-browser" bug for 2 years in our massive angularjs app, we got rid of all browsers but PhantomJS in our karma suite. PhantomJS' slowness, lagging-behind in webstandards and just my general gut feeling (these facts above made me question the point in running JavaScript tests in an actual browser at all) made me port our karma test suite to jest w/ jsdom and haven't been happier since we, years prior, got rid of our gnarly Selenium test suite that caught 0 bugs but was the major cause for maintenance headache.
- forgotpwtomain 10y ago> After we realised that we hadn't seen a "one-browser" bug for 2 years in our massive angularjs app Really? When I was writing JavaScript I thought I'd hit one ~ once a month. As a matter of fact I hit a v8 bug just yesterday which apparently doesn't support /Etc/GMT[-+][0-9]{0,2} timezones.
- deleted 10y ago[deleted]