Start reqlite server programmatically instead of using child.spawn()

Author: yamalight

server/package.json

@@ -8,7 +8,7 @@
     "db:start": "docker run -d -p 28015:28015 -p 8090:8080 -v $PWD/db:/data --name expertsdb rethinkdb",
     "db:stop": "docker stop expertsdb",
     "db:rm": "docker rm expertsdb",
-    "test": "eslint src/ && NODE_ENV=testing node test/index.js | tap-spec"
+    "test": "eslint src/ && node test/index.js | tap-spec"
   },
   "keywords": [
     "rest",

server/test/index.js

@@ -1,13 +1,12 @@
 /* eslint global-require: 0 */
-// get spawn
-const spawn = require('child_process').spawn;
+// say we're testing to evade excessive logging
+// usage of process.env is workaround for issues with setting env vars in windows
+process.env.NODE_ENV = 'testing';
 // require babel require hook
 require('babel-core/register');
-// reqlite instance
-const reqlite = spawn('reqlite');
-// wait for start
-reqlite.stderr.on('data', () => {
-  // require main tests
-  const startTests = require('./main').default;
-  startTests(reqlite);
-});
+// create reqlite instance
+const ReqliteServer = require('reqlite');
+const server = new ReqliteServer({silent: true});
+// require and start main tests
+const startTests = require('./main').default;
+startTests(server);

server/test/main.js

@@ -30,7 +30,7 @@ export default (reqlite) => {
     // close db connections
     test((t) => {
       setImmediate(() => r.getPoolMaster().drain());
-      reqlite.kill();
+      reqlite.stop();
       t.end();
     });
   });