fix: response.complete must be true after res.end

Fixes #1493

https://nodejs.org/dist/latest-v10.x/docs/api/http.html#http_message_complete

lib/request_overrider.js

@@ -556,6 +556,8 @@ function RequestOverrider(req, options, interceptors, remove, cb) {
               } else {
                 debug('ending response stream')
                 response.push(null)
+                // https://nodejs.org/dist/latest-v10.x/docs/api/http.html#http_message_complete
+                response.complete = true
                 interceptor.scope.emit('replied', req, interceptor)
               }
             })

tests/test_request_overrider.js

@@ -429,3 +429,30 @@ test("mocked requests have 'method' property", t => {
   })
   req.end()
 })
+
+// https://github.com/nock/nock/issues/1493
+test("response have 'complete' property and it's true after end", t => {
+  const scope = nock('http://example.test')
+    .get('/')
+    .reply(200, 'Hello World!')
+
+  const req = http.request(
+    {
+      host: 'example.test',
+      method: 'GET',
+      path: '/',
+      port: 80,
+    },
+    res => {
+      res.on('end', () => {
+        t.is(res.complete, true)
+        scope.done()
+        t.end()
+      })
+      // Streams start in 'paused' mode and must be started.
+      // See https://nodejs.org/api/stream.html#stream_class_stream_readable
+      res.resume()
+    }
+  )
+  req.end()
+})