considering

An assertion to document business rules / user stories

Changelog:

v 0.3.7: Testing custom client/server socket communication, continuing with Gatsby work, parts 4 and 5 of the tutorials
v 0.3.6: Adding socket React component, and journal.io for the server side (WIP), continuing on Gatsby site exploration (WIP), with part 3 of the tutorial
v 0.3.5: Continuing on Gatsby site exploration (WIP), with part 2 of the tutorial
v 0.3.4: Implementing Gherkin statement features (WIP), working on specs and TDD for consider.a.directory statement
v 0.3.3: Starting an experiment on Gatsby https://www.gatsbyjs.com/tutorial/part-two/, created a site on "site" sub-folder
v 0.3.2: (WIP) Added cucumber for testing, started with basic consider.a.file testing
v 0.3.1: Packages.js update of main file
v 0.3.0: Automatic dependencies update
v 0.2.10: Testing CI (WIP 3)
v 0.2.9: Test small fix, documentation updates;
v 0.2.8: Finished Implementing article "userStoryFile";
v 0.2.7: Implemented article "userStoryFile" (WIP);
v 0.2.6: Adding groupWith as function to create/add to epic (WIP);
v 0.2.5: Working on correlations being returned from the purpose method; bug fixes;
v 0.2.4: Minor fixes;
v 0.2.3: (WIP) working on correlation object, in trying to find correlations between actions and users;
v 0.2.2: Implementing epic append method, preparing other unit tests for next improvements;
v 0.2.1: Implementing userStory unit tests - epics (WIP);
v 0.2.0: Implemented summary outputs from statementsFile. userStoryFile still in progress;
v 0.1.9: Started working on userStoryFile class (WIP for remaining general unit tests)
v 0.1.8: More Bug fixes. Implemented eachTagged Determiner
v 0.1.7: Bug fixes. Implemented Reading and deserializing from a statements file
v 0.1.6: Working on tagging statements in files (WIP). Created byTagDeterminer which selects only elements with given criteria. Started creting a statementsFile entity which inherits file and allows saving more context of each sentence (e.g. Tags, etc...)
v 0.1.5: Working on statement files (WIP);
v 0.1.4: Working on file and user story test cases - added action and purpose iterators;
v 0.1.3: Working on user story unit tests - can extract the user from a user story.
v 0.1.2: Working on converting a statement object to a user story. Building user story members and use cases (WIP). Setup of badges and travis build (WIP).
v 0.1.1: Adding travis-ci configuration files (draft, WIP), declaring strict mode in JS files.
v 0.1.0: Working on whether a statement has a purpose. Added Error handler file. Continuing the documentation of the code. Current Unit tests are in progress.
v 0.0.10: Minor changes, saving chai and chai-as-promised in the package as dependencies. Started building documentation using https://www.npmjs.com/package/documentation package. Started documenting code. Documentation output should be in "md" format to be easily accessible and readable from github and npm online.
v 0.0.9: Adding modal verbs, continuing on verification if statement has a proper user story format. Introducing base class 'base' where all other classes inherit from; Introducing types of verbs:

• Modal verb;
• Auxiliary verb;

v 0.0.8: Working on determiner "first" and "last" for object statements. WIP on iterator object.
v 0.0.7: Continuation isUserStoryFormat, created userStory class, and static methods for checking if user, action and purpose exist, which can be caled without instantiating the class.
v 0.0.6: Added more user advanced Unit tests, added tag and unTag functions, WIP next on isUserStoryFormat
v 0.0.5: Added count, find functions and determiner "word" in statement class.
v 0.0.4: Added functions to handle file lines as statements
v 0.0.3: Added file reading. Created class conjunction (for where), and it's connecting determiners, each or every, which are instances of determiner class, created setDeterminer method to inject functions to the determiners dinamically, like the 'file' object which will require a file.where.each."line" method.
v 0.0.2: Started creating first classes, stubs , main class, articles, objects, working on unit tests (WIP)
v 0.0.1: First versions with Unit tests;

DOCUMENTATION

Consult the documentation here

For generating a coverage badge:
export MOCHA_BADGE_SUBJECT=mocha export MOCHA_BADGE_OK_COLOR=green export MOCHA_BADGE_KO_COLOR=orange export MOCHA_BADGE_STYLE=flat

mocha --reporter mocha-reporter-badge > badge.svg