Module to mock browser in node
Synchronous browser mock shims.
Synchronous browser mock shims.
Seamless REST/GraphQL API mocking library for browser and Node.js.
The node core libs for in browser usage.
Mock a canvas in your jest tests.
This library emulates ioredis by performing all operations in-memory.
fetch mock for jest
Axios adapter that allows to easily mock requests
Mock http requests made using fetch
Eventus mini-app SDK with an explicit browser mock mode.
No description provided.
fetch mock for vitest
Jest hooks for JSDOM location mock
The node core libs for in browser usage.
Mock HTTP server for testing HTTP clients and stubbing webservices
🌗 A module used to mock canvas in Vitest.
Easy and powerful mocking of AWS SDK v3 Clients
<!-- automd:badges color=yellow -->
Mock localStorage for headless unit tests
A Mock API for AWS Kinesis
Type safe mocking extensions for jest
Vitest wrapper for fetch-mock
jest wrapper for fetch-mock
A development tool that renders Shopify Liquid templates locally with mock data, providing a browser-based preview for sections and snippets.
Fork of travishaynes/shopify-mock This gem is used for testing Shopify apps without having to actually connect to Shopify to develop the application. You can use this gem explicitely for testing, or you can also use it in your development environment to speed things up when fiddling around in the web browser, or in the console.
Enhances the ActionMailer Previews introduced in 4.1 by automatically creating ActionMailer Previews at runtime in development mode. See automatic previews of your ActionMailer emails, with no extra effort or mock data. Install the action_mailer_auto_previews gem into your :development group, and it'll 'just work' with sensible defaults. Each ActionMailer email object that has .deliver or .deliver_later called will automatically launch your default browser right to a ActionMailer Preview page with the real data passed to that email. Flexible options allow you to alter this behavior as well. Warning: Since this is dynamically creating Ruby classes/methods, you will want to make sure your web-server is single threaded. For example, if you're using Puma, be sure to set the `workers` configuration parameter to 1.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.