Question 1

How do I simulate a server timeout with jQuery Mockjax?

Accepted Answer

Set the 'isTimeout' property to true in your mock definition. Combined with 'responseTime', this forces jQuery to treat the request as timed out, triggering error callbacks, as explained in the 'Forced Simulation of Server Timeouts' section.

Question 2

Can Mockjax be used in Node.js or with Browserify?

Accepted Answer

Yes, Mockjax supports Node.js and Browserify by requiring it with jQuery and a window object, as detailed in the 'Using Mockjax in Other Ways' section. However, you must provide these dependencies manually in non-browser environments.

Question 3

What's the difference between Mockjax and Sinon.js for AJAX mocking?

Accepted Answer

Mockjax is tailored for jQuery's AJAX and integrates seamlessly with minimal setup, while Sinon.js is a general-purpose mocking library that can stub any function but requires more configuration for jQuery. Mockjax is simpler for jQuery-centric projects, but Sinon.js offers broader framework support.

Question 4

How to clear all Mockjax handlers after running tests?

Accepted Answer

Call $.mockjax.clear() without arguments to remove all handlers and reset the state. For individual handlers, use $.mockjax.clear(id) with the handler ID or a URL string/regex, as described in the 'Removing Mockjax Handlers' section.

Question 5

Does Mockjax support mocking JSONP requests?

Accepted Answer

Yes, Mockjax can mock JSONP requests as it handles various data types, including Script. Ensure the URL matching accounts for callback parameters, and use responseText or callbacks to define the response, as mentioned in the 'Data Types' section.

Question 6

How to mock dynamic responses based on request data in Mockjax?

Accepted Answer

Use the 'response' callback function in your mock definition. It receives the request settings, allowing you to inspect data and set this.responseText or this.responseXML dynamically, with examples in the 'Dynamically Generating Mock Responses' section.

Question 7

Mockjax or using a real backend for development: which is better?

Accepted Answer

Mockjax excels in rapid frontend prototyping and unit testing without a backend, but for integration or end-to-end testing, a real or more comprehensive mocked server might be necessary. It's ideal for isolated frontend development but not a full backend replacement.

Mockjax

What is Mockjax?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions