test: update remaining tap asserts

After the previous changes there were a few lingering asserts that
didn't match the names in the newest version of tap. These were
relatively trivial to fix, although interestingly the meaning of the
'includes' synonym changed at some point from "match" to "has"; these
tests were written at the time "includes" meant "match".

Author: KernelDeimos

test/cli.test.js

@@ -34,7 +34,7 @@ function checkServerIsRunning(url, msg, t, _cb) {
 }
 
 function tearDown(ps, t) {
-  t.tearDown(() => {
+  t.teardown(() => {
     ps.kill('SIGTERM');
   });
 }

test/main.test.js

@@ -57,8 +57,8 @@ test('http-server main', (t) => {
             requestAsync("http://localhost:8080/").then(res => {
               t.ok(res);
               t.equal(res.statusCode, 200);
-              t.includes(res.body, './file');
-              t.includes(res.body, './canYouSeeMe');
+              t.match(res.body, './file');
+              t.match(res.body, './canYouSeeMe');
 
               // Custom headers
               t.equal(res.headers['access-control-allow-origin'], '*');

test/process-env-port.test.js

@@ -40,7 +40,7 @@ function startServer(url, port, t) {
     });
   } else {
     ecstatic.on('exit', (evt) => {
-         t.notEqual(evt.code, 0, 'err:Running on invalid port not allowed');
+         t.not(evt.code, 0, 'err:Running on invalid port not allowed');
     });
   }
 }