I have found the Javascript/DOM tests, especially for the simple interactions that you are describing, are not that useful. You’ll testing that things are set up right, and since jQuery is so declarative, your tests look a lot like your code. My current thinking is that if you are writing larger JS components, it makes … Read more
For mocking ajax requests, you can try something like this… Here’s the function you want to test: var functionToTest = function () { $.ajax({ url: ‘someUrl’, type: ‘POST’, dataType: ‘json’, data: ‘foo=1&foo=2&foo=3’, success: function (data) { $(‘#main’).html(data.someProp); } }); }; Here’s the test case: test(‘ajax mock test’, function () { var options = null; jQuery.ajax … Read more
This is either because in the result of a promise or any other deferred code you do not check the destroy status of an object, or because you didn’t teardown something that has been setup and interact with DOM events or anything external to the core of Ember. I used to have this especially on … Read more
I think that Jack is the best mocking framework for JavaScript as of the time of this writing. The main reason is that what’s right for JavaScript is not likely what is right for a strongly typed language such as Java. Many JavaScript mocking frameworks are inspired by Java mock frameworks (such as the excellent … Read more
None of the posted answered worked for me because of our configuration of TypeScript and React (tsx) we’re using. Here’s what finally worked: beforeEach(() => { // IntersectionObserver isn’t available in test environment const mockIntersectionObserver = jest.fn(); mockIntersectionObserver.mockReturnValue({ observe: () => null, unobserve: () => null, disconnect: () => null }); window.IntersectionObserver = mockIntersectionObserver; });
That is because the == operator doesn’t compare only primitives, therefore doesn’t call the valueOf() function. Other operators you used do work with primitives only. I’m afraid you cannot achieve such thing in Javascript. See http://www.2ality.com/2011/12/fake-operator-overloading.html for some more details.
QUnit is very easy to get started with, as you only need to include two files and a little bit of markup, then you can start writing tests. Jasmine strength, afaik is its BDD-style syntax, if that is something that you prefer (probably not a selling point for you) and tight integration into Ruby/Rails tools. … Read more