What is the goal of chai-spies? about chai-spies HOT 3 CLOSED

@keithamus @meeber probably I can share my vision of chai spies:

Robust, easy to use library with nice chai integration

Few reasons why I don't like sinon:

• too much terms with different methods (stub, spy, whatever)
• in order to use sinon you need to go through the whole docs and eventually you will not find answer to your question.
• integrates badly with chai. in chai each word separated with dot but with sinon and sinon-chai you will write something like expect(spy).to.have.been.calledWith what looks odd in context of other specs

On the other hand chai-spies something intuitive, you dont need much docs. Just few methods. And then it's easy to guess like:

const spy = chai.spy()
const returnFive = chai.spy.returns(5) // so, you write what you need: `spy returns 5` I haven't seen more obvious way to do it in js frameworks
const array = []
chai.spy.on(array, 'push') 
expect(array.push).not.to.have.been.called()

const interface = chai.spy.object({ run: null })
expect(interface.run).not.to.have.been.called()

Also I think the main goal of this ticket is to change README file to highlight this.

Does it make sense?

from chai-spies.

@meeber do you have any thoughts on this?

from chai-spies.

I think it's clear that some people prefer chai-spies over sinon-chai, and that the features being requested recently can be implemented without sacrificing the qualities that make them prefer chai-spies. So, more power to this plugin!

from chai-spies.