test.replication: remove "down-server"

The naming of the replication test which accessed the "down server" implies it's
attempting to connect to a server which is down.  The test actually passed for
any non-pouchdb server, including:

* a hostname which doesn't resolve
* a hostname which resolves but server does not respond
* a server which responds, but not as a couch server

Author: alxndrsn

bin/down-server.js

@@ -12,12 +12,6 @@ else
 fi
 
 if [ $TYPE = "integration" ]; then
-    if  (: < /dev/tcp/127.0.0.1/3010) 2>/dev/null; then
-        echo "down-server port already in use"
-    else
-        node bin/down-server.js 3010 & export DOWN_SERVER_PID=$!
-    fi
-
     TESTS_PATH="tests/integration/test.*.js"
 fi
 if [ $TYPE = "fuzzy" ]; then

bin/test-node.sh

@@ -4260,15 +4260,14 @@ describe('suite2 test.replication.js-down-test', function () {
   });
 
   it('replicate from down server test', async () => {
-    const source = new PouchDB('http://127.0.0.1:3010', {
+    // localhost port 6 is reserved, and should not be in use.  This aims to emulate
+    // the original intent of this test, which apparently used a registered domain
+    // name which would resolve, but not respond to HTTP requests.
+    const source = new PouchDB('http://localhost:6', {
       ajax: {timeout: 10}
     });
     const target = new PouchDB(dbs.name);
-    try {
-      await source.replicate.to(target);
-    } catch (error) {
-      should.exist(error);
-    }
+    await source.replicate.to(target).should.be.rejectedWith(/^Failed to fetch$/);
   });
 });