Incorrect setUp example in README

Environment

There is a bug in the README doc in the Responses inside a unittest setUp() section. At the moment the docs say that you should add stop BEFORE reset to the cleanUp functions but since cleanups are run in reversed order this is incorrect. In this configuration you won’t be able to check if every mock was called since the reset will reset the responses mock’s list and stop won’t have anything to check. You can check this out by investigating the unittest.TestCase class.

`

def doCleanups(self):
    
    outcome = self._outcome or _Outcome()
    while self._cleanups:
        function, args, kwargs = self._cleanups.pop()
        with outcome.testPartExecutor(self):
            function(*args, **kwargs)
            
    # return this for backwards compatibility
    # even though we no longer us it internally
    return outcome.success

`

As you can see there is a .pop() call that pop the LAST element from the list.

Steps to Reproduce

1. You can reproduce this by simply doing a TestCase with 1 mocked response and changing the order of the functions added to cleanups

Expected Result

The reset should be added to cleanups BEFORE the stop function. The docs should be:

`

def setUp():
     self.responses = responses.RequestsMock()
     self.responses.start()

     # self.responses.add(...)

     self.addCleanup(self.responses.reset)
     self.addCleanup(self.responses.stop)


def test_api(self):
    self.responses.add(
        responses.GET, 'http://twitter.com/api/1/foobar',
        body='{}', status=200,
        content_type='application/json')
    resp = requests.get('http://twitter.com/api/1/foobar')
    assert resp.status_code == 200

`

[beliaev-maksim]

@itsdkey glad it helps 😃

[itsdkey]

okay, this can be good 😄