effects-as-data - npm Package Compare versions

Comparing version 2.14.2 to 2.14.3

package.json

		{
		"name": "effects-as-data",
		"version": "2.14.2",
		"version": "2.14.3",
		"description":
		@@ -5,0 +5,0 @@ "A micro abstraction layer for Javascript that makes writing, testing, and monitoring side-effects easy.",

README.md

		@@ -218,3 +218,3 @@ # Effects-as-data

		Its important to note that effects-as-data tests cover 1 full code path through a function. Effects-as-data are thorough (on a mathematical level): your test CANNOT leave things out or skip things in a given code path. If your function has 2 code paths (because of something like an `if`), you'll need at least 2 tests. The nice thing about effects-as-data tests is that they combine the Chicago and London schools of testing. An effects-as-data test will ensure that your side effects happen in the right way, in the right order, and in the right number of times, but only by checking state. Its the best of both schools of thought.
		Its important to note that effects-as-data tests cover 1 full code path through a function. Effects-as-data tests are thorough (on a mathematical level): your test CANNOT leave things out or skip things in a given code path; if you do, your test will fail. If your function has 2 code paths (because of something like an `if`), you'll need at least 2 tests. The nice thing about effects-as-data tests is that they combine the Chicago and London schools of testing. An effects-as-data test will ensure that your side effects happen in the right way, in the right order, and in the right number of times, but only by checking state (i.e. effects represented as state / data). Its the best of both schools of thought.

		@@ -221,0 +221,0 @@ Below are a few examples of testing with effects-as-data:

New alerts