stub.resetBehavior() missing in documentation

[ikokostya]

sinon 1.6.0

Method stub.resetBehavior() looks like public but it missing in documentation.
What difference between stub.yields() and stub.thenYields()?

[mantoni]

There is still work being done regarding resetBehavior (see #244 ). I'm not sure whether it should be documented already.

The same goes for thenYields. The idea is to yield on the first invokation and thenYield on another invokation. This might change again in favor of onCall(n).yields(...).

[ikokostya]

@mantoni How can I override previous yields() in sinon 1.6.0?

[mantoni]

Could you send a more detailed description of what you are trying to do to the mailing list?

[faridnsh]

@mantoni The problem of resetBehavior is inconsistency when withArgs is used?

[mantoni]

Is it? To be honest, I don't really know. Maybe it could be added to the documentation now, but I'm unsure whether it should really become an "official" part of the API. The ideas developed in the mentioned issue might lead to the function being obsolete - if we ever find the time to finally work on it.
@cjohansen What is your opinion on this?

[cjohansen]

I don't think it should be documented as it won't be needed in the future.

[dotchev]

I still find resetBehavior useful and worth documenting.

Consider this code

var stub = sinon.stub();
stub.withArgs(1).returns('Bye');

How would you reset this stub to always return 'Hello' for example.
Just doing stub.returns('Hello') does not work.
But this does work

var stub = sinon.stub();
stub.withArgs(1).returns('Bye');
stub.resetBehavior();
stub.returns('Hello');
// stub(1) now returns 'Hello', i.e. old stubbings are reset

Generally it makes a lot of sense to be able to reset all behavior-related changes on a stub.
It would be very useful to clean/reset the stub at the end of each test case.

[mroderick]

Please don't revive issues that have been closed for years.

We are trying to keep the GitHub issues list tidy and focused on bugs and feature discussions. If you have usage questions, please post them to the Sinon.JS mailinglist, so the bigger community can help answer your questions.

If you believe that you've found a bug in Sinon.JS, please open a brand new ticket and follow the guidelines for reporting an issue.