I recently came across a tutorial on TDD React here and I'm having trouble understanding the following test scenario:
it('Correctly updates the state after AJAX call in `componentDidMount` was made', (done) => {
nock('https://api.github.com')
.get('/users')
.reply(200, [
{ 'name': 'Reign', 'age': 26 }
]);
// Overwrite, so we can correctly reason about the count number
// Don't want shared state
wrapper = mount(<UsersListComponent />);
setTimeout(function() {
expect(wrapper.state().usersList).to.be.instanceof(Array);
expect(wrapper.state().usersList.length).to.equal(1);
expect(wrapper.state().usersList[0].name).to.equal('Reign');
expect(wrapper.state().usersList[0].age).to.equal(26);
nock.cleanAll();
done();
}, 1500);
});
I'm confused about why nock is being used to fake a request in this test case. The request itself seems to be pointless and I'm unsure of where the response is directed towards. In my understanding of TDD, I thought the approach was to write the test (the code starting at wrapper), watch it fail, and then incorporate a real ajax call within the actual component for testing. I just don't see the purpose of using nock here.