feat: testing guidelines

docs/drafts/testing-guidelines.md

@@ -16,7 +16,10 @@ The minimal versions you should focus are:
 * LTS (long time support)
 * Current
 
-Of course, you are freely to maintain a package that run also with older versions of Node.js that reach the "end-of-life" stage.
+Supporting older versions of node is encouraged where practical.
+
+For browser-based modules and modules that are designed to work equally both client and server side it is essential to test on various 
+versions of your target browser and to publish which environments are supported.
 
 ### How?
 It is a good idea to have unit tests, coverage that matches most use cases for the module, and make sure things work in all supported environments.
@@ -25,9 +28,31 @@ It is a good idea to have unit tests, coverage that matches most use cases for t
 * **integration test**: test your code with other applications dependencies
 * **acceptance test**: test your application sticks in performance, heavy load, etc..
 
-Here are some things to consider as you develop your package.
+#### Unit Testing
+The initial and fundamental start of any testing strategy should start with a unit testing strategy. For the JavaScript language
+the unit test may be the first place to catch code that will not parse. It is also the way to define the expectation for a particular
+function or code block. The unit test should describe what to expect from that code when given a defined set of inputs.
+
+For a test to be considered a unit test it should consume no remote services.
+
+It is generally considered good practice to run units as part of any commit or build strategy.
+
+#### Integration Testing
+Integration testing in general requires that the code under test be in a package.
+
+For many packages integration testing requires that the built package be run via a testing tool upon several environments. The /
+field of continuous integration and deployment (CI/CD) is complex. The package being built shall be run through
+a CI/CD pipeline. Several integrations are available for GitHub based repositories. (There are also alternatives to GitHub.)
+
+For many open source projects on Github free integration environments are available.
+
+#### Acceptance Testing
+Every package will have different criteria for acceptance. The maintenance committee has particular interest in making sure
+that dependents of packages are not impacted by the release of a new version. We encourage liaison between both the
+publisher and the dependents where possible.
+
+### Links to some useful tools
 
-Some useful tools:
 * [c8](https://www.npmjs.com/package/c8)
 * [citgm](https://www.npmjs.com/package/citgm)
 * [Codecov](https://www.npmjs.com/package/codecov)
@@ -37,3 +62,7 @@ Some useful tools:
 * [Nock](https://www.npmjs.com/package/nock)
 * [nyc](https://www.npmjs.com/package/nyc)
 * [tape](https://www.npmjs.com/package/tape)
+* [Github CICD](https://docs.github.com/en/actions/building-and-testing-code-with-continuous-integration/about-continuous-integration)
+* [Gitlab](https://about.gitlab.com/)
+* [Circle CI](https://circleci.com/product/)
+* [Travis CI](https://travis-ci.com/)