Merge branch 'master' of https://github.com/jan-molak/serenity-js

book/design/assertions.md

@@ -52,15 +52,15 @@ items => expect(items).to.eventually.include.('some item of interest');
 could be made configurable:
 
 ```typescript
-expected => actual => expect(items).to.eventually.include(expected);
+expected => actual => expect(actual).to.eventually.include(expected);
 ```
 
 We could also give the above function a name, and store it in our project as, say `assertions.ts`, so that
 it can be reused in other scenarios:
 
 ```typescript
 // assertions.ts
-export include = expected => actual => expect(items).to.eventually.include(expected);
+export include = expected => actual => expect(actual).to.eventually.include(expected);
 ```  
 
 With this one-liner in place, we could improve the task definition from the previous example:

packages/integration-testing/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@serenity-js/integration-testing",
-  "version": "2.0.0",
+  "version": "4.0.0",
   "description": "Internal module to help test integration of Serenity/JS with test runners and frameworks",
   "author": "Jan Molak <jan.molak@smartcodeltd.co.uk>",
   "homepage": "http://serenity-js.org",

packages/serenity-js/package.json

@@ -1,6 +1,6 @@
 {
   "name": "serenity-js",
-  "version": "1.8.0",
+  "version": "1.8.1",
   "description": "Serenity/JS: Next generation acceptance testing library for modern web applications.",
   "author": "Jan Molak <jan.molak@smartcodeltd.co.uk>",
   "homepage": "http://serenity-js.org",