yet another spy library
A simple spy.
Simple spy function for unit testing
Lightweight Jest compatible spy implementation
spy on outgoing requests in node
Hex Dumper (streaming, sync, and cli)
A simple little class that helps making Observable testing a breeze
A debugging library for RxJS
A minimal fork of nanospy, with more features
detect in-app browsers
spy and mock for simple testcase
A through2 wrapper to for simple stream.PassThrough spies.
mock mate, mock http request, fs access and so on.
A through2 wrapper that just receives chunks and nothing else.
Spies for the Chai assertion library.
<a href="CODE_OF_CONDUCT.md"><img src="https://img.shields.io/badge/Contributor%20Covenant-v2.0%20adopted-ff69b4.svg" alt="Contributor Covenant" /></a>
Render preact components with access to the produced virtual dom for testing.
parse user agent string to human readable object like os, device, browser, etc
Lightweight Mock Object Testing For Javascript.
Just a spy library.
Minimal spy library with pass-through
Extends Chai with assertions for the Sinon.JS mocking framework.
RxJS DevTools plugin for rxjs-spy
<p align="center"><a href="https://tridiamond.tech" target="_blank" rel="noopener noreferrer"><img width="100" src="https://img-blog.csdnimg.cn/20200930013332450.png" alt="TriDiamond logo"></a></p>
Spy is a mocking library that was made for the modern age. It supports only 2.1.0+. Spy by default will raise an error if you attempt to stub a method that doesn't exist or call the stubbed method with the wrong arity.
A gem for simple mocking and spying in Ruby's MiniTest framework.
Remember when RSpec had stub_chain? They removed it for good reasons but sometimes you just need it. Well, here it is, a proxy object. It doesn't actually mock anything for you (the name is just catchy) so you need to do that. But that actually comes with a lot of benefits: 1) It's compatable with any testing framework 2) You can use it for purposes other than testing, e.g. prototyping, code stubs 3) Flexibility in how you use it without overloading the number of methods you have to remember Here's an example usage: let(:model_proxy) do MockProxy.new(email_client: { create_email: { receive: proc {} } }) end before { allow(Model).to receive(:new).and_return model_proxy } it 'should call receive' do proc = MockProxy.get(model_proxy, 'email_client.create_email.receive') expect(proc).to receive(:call) run_system_under_test MockProxy.update(mock_proxy, 'email_client.create_email.validate!') { true } MockProxy.observe(mock_proxy, 'email_client.create_email.send') do |to| expect(to).to eq 'stop@emailing.me' end run_system_under_test2 end As you can see, the proc - which ends the proxy by calling the proc - can be used for anything. You can spy on the call count and arguments, mock methods, or just stub out code you don't want executed. Because it doesn't make any assumptions, it becomes very flexible. Simple, yet powerful, it's uses are infinite. Enjoy
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.