v0.9.3

.gitignore

@@ -1,3 +1,4 @@
 node_modules
 coverage
 
+package-lock.json

.travis.yml

@@ -1,9 +1,9 @@
 language: node_js
 node_js:
+  - "14"
+  - "12"
   - "10"
   - "8"
-  - "7"
-  - "6"
 
 after_success:
   npm run coveralls

CHANGELOG.md

@@ -1,8 +1,16 @@
 e2e-helper
 ==========
+<<<<<<< HEAD
+=======
+## 0.9.4
+  - setup - fix - pass error to `done` when SUT fails to start
+  - include node v12.x and v14.x in tests
+>>>>>>> 06e7a2f8f10679e30c40c5cd3a75b91e83ec2c7a
+
 ## 0.9.3
+  - setup - fix - pass error to `done` when SUT fails to start
   - add in Readme.md the undocumented feature: `options.env`
-  - include node v10.x in tests
+  - include node v10.x v12.x and v14.x in tests
 
 ## 0.9.2
   - fix bug: kill timeouts should be `.unref()`ed

README.md

@@ -40,18 +40,18 @@ The returned value is the setup handler, where the teardown handler is found bot
 
 e.g.:
 ```
-const setup = require('e2e-helper')({ 
+const setup = require('e2e-helper')({
   svc:   'bin/server',
   readyNotice: 'server is started'
-}) 
+})
 
 //setup --> function(done) { ... }
 //setup.teardown -->  function(done) { ... }
 
 declare('my service', () => {
    before(setup);
    after(setup.teardown);
-   
+
    require('./api-1.test.js');
    require('./api-2.test.js');
    require('./api-3.test.js');
@@ -96,8 +96,9 @@ All 3 mocha facilitators are using the same lower-level mechanism to retrieve th
 To make sure the setup and teardown are called first and last respectively - all the suites are loaded to the same root tests tree.
 For this - the passed `options` should include them as well.
 
-### Additional option supported in mocha facilitators
+### Additional options supported in mocha facilitators
  - `suites` - array of strings - paths relative to `process.cwd()` (or absolute) of suites to run between setup and teardown.
+ - `title` - passed as 1st argument to the `describe` that will hold the setup, teardown, and all the passed suites. defaults to `end-to-end`
 
 ## with mocha, bdd ui
 
@@ -126,7 +127,7 @@ which is ran as `npm e2e`, which in turn is configured to run as:
     "e2e": "mocha test-ete/index.js",
 ```
 
-**NOTE:** If you want to test your server in few execution modes - you may for example provide few files in the fassion that `test-e2e/index.js` is portrayed here, 
+**NOTE:** If you want to test your server in few execution modes - you may for example provide few files in the fassion that `test-e2e/index.js` is portrayed here,
 and configure your `npm e2e` to run all these test-roots.
 
 
@@ -138,7 +139,7 @@ require('e2e-helper').bdd({
 
 ## with mocha, tdd ui
 
-Almost exactly like `mocha bdd ui`, only that in stead of 
+Almost exactly like `mocha bdd ui`, only that in stead of
 ```
 require('e2e-helper').mocha_bdd({
   ...
@@ -157,7 +158,7 @@ require('e2e-helper').tdd({
 
 ## with mocha, using the mocha-ui-exports plugin
 
-Almost exactly like `mocha bdd ui`, only that in stead of 
+Almost exactly like `mocha bdd ui`, only that in stead of
 ```
 require('e2e-helper').mocha_bdd({
   ...

package.json

@@ -1,6 +1,6 @@
 {
   "name": "e2e-helper",
-  "version": "0.9.2",
+  "version": "0.9.3",
   "description": "end-to-end test helper, with facilitators for mocha",
   "main": "lib",
   "repository": {
@@ -22,7 +22,7 @@
     "coveralls": "^3.0.0",
     "eslint": "^4.15.0",
     "istanbul": "*",
-    "mocha": "~2.3.4",
+    "mocha": "^7.2.0",
     "mocha-ui-exports": "^1.1.0",
     "should": "^9.0.0"
   },