risei 1.3.3 → 1.3.4

package/README.md

@@ -8,8 +8,6 @@
 * Refactor or replace existing designs without worrying about the cost in past or future test time.
 * Create tests with immediate confidence, because you can't introduce mistakes in test code you write.
 
-Risei may be referred to as **Rs** here for brevity.
-
 
 
 
@@ -472,7 +470,7 @@ Testing TypeScript code with Risei basically just means transpiling before runni
 
 If you follow the general Risei set-up, you can just make the following few modifications for TypeScript applications.
 - These steps have worked with both Angular and React.
-- Variant approaches are also sure to work, depending on the other technical choices in play.
+- Varying other approaches are also sure to work, depending on the other technical choices in play.
 
 
 
@@ -568,26 +566,46 @@ Two issues are known to exist:
 
 - When a few properties are changed in separate objects, they are treated as whole new tests, which usually fail because of their unintended mix of old and new properties.
   - To avoid this problem, just change properties as part of whole new tests, or else restate `.of` along with the changed properties.
-  - Rs is actually working as intended when this happens, but ways to optionally prevent it are being considered.
+  - Risei is actually working as intended when this happens, but ways to optionally prevent it are being considered.
 
 
 
 ## What's new in Risei
 
+- Release **1.3.4** (March, 2024) fixes a bug that caused class definitions still to appear instead of class names when classes were used as object properties.
+  - As a side effect of this change, objects' own `toString()` is never used in onscreen test output any longer, but all of Risei's output display is now handled the same.
+
+
 - Release **1.3.3** (March, 2024) fixes a major bug related to file paths that prevented any tests from loading or running in Windows environments.
+  - Risei is now fully usable in Windows environments again.
+
+
+- Release **1.3.2** (February, 2024) does not change the code at all, but improves this read-me.
+  - It now explains the easiest way to deal with mutable args (which is just restating the args).
+  - A few mistakes in the text were also fixed.
 
-- Release **1.3.2** (February, 2024) does not change the code at all, but improves this read-me, notably explaining the easiest way to deal with mutable args (which is just restating the args), and correcting a few mistakes.
 
-- Release **1.3.1** (February, 2024) reverses some changes in 1.3.0 that were intended to fully isolate tests against mutable args, but which caused incomplete or inaccurate object contents in some cases.   This sort of built-in total isolation is not feasible, and in fact is rarely needed.
+- Release **1.3.1** (February, 2024) reverses some changes in 1.3.0 that were intended to fully isolate tests against mutable args, but which caused incomplete or inaccurate object contents in some cases.
+  - Supporting built-in total test isolation is not feasible with collapsing forward, nor is it usually necessary given easy usage alternatives.
+  - In contrast, collapsing forward is both highly beneficial and frequently used.
 
-- Release **1.3.0** (February, 2024) moves the display of test-loading error messages to a new gold bar that appears at the bottom of the summary when there are any loading errors.   A sorting error that occurs when no test files exist yet has also been fixed. 
 
-- Release **1.2.0** (January, 2024) changes sorting of test files.   Previously they were displayed in the order found.   Now the order remains the same, except that the last-edited file is moved to the bottom, making it easy to see the latest test results.
+- Release **1.3.0** (February, 2024) makes two changes:
+  - If there are any test-loading errors, their messages now appear in a new gold bar that appears below the summary of the test run.
+  - A test-sorting error has also been fixed that occurred when no test files existed yet. 
+
+
+- Release **1.2.0** (January, 2024) changes sorting of test files to make tests you're working on now appear at the bottom.
+  - Previously tests were displayed in the order found, which is always alphabetical (though is not guaranteed to be so).
+  - The order for all files except one remains the same.
+  - The last-edited file is moved to the bottom, making it easy to see the latest test results.
+
 
 - Release **1.1.2** of Risei (January, 2024) fixes two problems:
   - Classes were sometimes displayed in output as their entire definition.   Now just the class name is displayed.
   - All `Date` instances were considered equal, regardless of their actual value.   Now they only are considered equal when they actually are.
 
+
 - Don't use release **1.1.1**, which contains an internal path error.
 
 

package/package.json

@@ -1,18 +1,21 @@
 {
   "name": "risei",
-  "version": "1.3.3",
-  "description": "Risei is the framework that allows you to write unit tests as collections of values in JavaScript objects, so it's easy and fast, and tests don't serve as a drag on redesigns.",
+  "version": "1.3.4",
+  "description": "Risei is the framework that allows you to write unit tests as simple JavaScript objects, so it's easy and fast, and tests don't serve as a drag on redesigns.",
   "keywords": [
     "unit test",
     "test",
     "unit testing",
     "testing",
+    "test framework",
     "easy",
     "fast",
     "simple",
     "values",
     "objects",
-    "declarative"
+    "declarative",
+    "javascript",
+    "typescript"
   ],
   "author": "Ed Fallin <riseimaker@gmail.com>",
   "license": "MIT",

package/system/ClassPropertySpoofer.js

@@ -4,6 +4,9 @@ import { ASpoofingFixture } from "./ASpoofingFixture.js";
 import { SpoofDefinition } from "./SpoofDefinition.js";
 import { TypeAnalyzer } from "./TypeAnalyzer.js";
 
+/* &cruft, implement this under test so that anything that can be spoofed 
+           from the class level is spoofed, but not expecting it to get 
+           absolutely everything, and supporting poly-spoofing syntax */
 export class ClassPropertySpoofer extends ASpoofingFixture {
     /* Algorithm:  Forward method spoof() looks at spoof definitions in .plus and applies them 
                    to each class' prototypes after first saving the original member definitions.

package/system/ObjectPropertySpoofer.js

@@ -58,7 +58,7 @@ export class ObjectPropertySpoofer extends ASpoofingFixture {
 
         // Working only with property spoofs.
         let propertySpoofs = Array.from(spoofDefinitions)
-            .filter(x => TypeAnalyzer.memberIsProperty(test.on, x.on));
+            .filter(spoof => TypeAnalyzer.memberIsProperty(test.on, spoof.of));
 
         // Storing new values for setting.
         this.#settables = propertySpoofs;

package/system/TestStages.js

@@ -105,51 +105,6 @@ export class TestStages {
 
     // region Dependencies of test stages
 
-    #anyOriginalPropertyGetting(target, settables) {
-        if (!Array.isArray(settables)) {
-            return;
-        }
-    
-        let unsettables = [ ];
-        
-        for (let settable of settables) {
-            // Not a setter tuple.
-            if (!settable.of) {
-                continue;
-            }
-            
-            // Retaining original.
-            let original = target[settable.of];
-            let unsettable = { of: settable.of, as: original };
-            unsettables.push(unsettable);
-        }
-        
-        return unsettables;
-    }
-
-    #anyPropertySetting(target, settables) {
-        // No properties to set.
-        if (!Array.isArray(settables)) {
-            return;
-        }
-    
-        for (let settable of settables) {
-            // Not a setter tuple.
-            if (!settable.of) {
-                continue;
-            }
-
-            // Actually setting property.
-            target[settable.of] = settable.as;
-        }
-    }
-    
-    #anyPropertyUnsetting(target, unsettables) {
-        // Unsetting is the same as setting, 
-        // but with tuples of original values.
-        return this.#anyPropertySetting(target, unsettables);
-    }
-
     #compare(expected, actual) {
         return this.#comparer.compare(expected, actual);
     }

package/system/TotalDisplayer.js

@@ -104,17 +104,9 @@ export class TotalDisplayer {
     }
 
     displayObject(value) /* passed */ {
-        // Use toString() text if it's meaningful.
-        let asString = value.toString();
-
-        if (asString !== "[object Object]") {
-            return asString;
-        }
-
-        // If toString() not meaningful, list members.
+        // Each property of the object is handled individually.
         let items = [ ];
 
-        // Each property of the object is handled individually.
         for (let p in value) {
             // Cross-recursion.
             let item = this.display(value[p]);