risei 3.3.2 → 3.3.3

package/README.md

@@ -3,7 +3,7 @@
 
 ## Overview
 
-Risei is a new way to write unit tests that's easier and faster, more dependable, and keeps your tests from standing in the way of redesigns.
+Risei is a new way to write unit tests that's easier, faster, and more readable.   Tests made with Risei aren't a source of errors or a drag on redesigns.
 
 Risei does all this by replacing hand-coded tests with simple declarative syntax.
 
@@ -40,16 +40,15 @@ And they have a summary bar at the bottom:
 
 ![https://deusware.com/risei/images/Summary-example.png](https://deusware.com/risei/images/Summary-example.png)
 
-- This bar is red when any tests fail, much as you'd expect.
+- This bar is red when any tests fail, just as you'd expect.
 
 
 
 ## Status
 
-Risei's major features are now complete, but new enhancements or fixes may appear from time to time. \
-The latest release, **3.3.2**, adds `async` capabilities formerly missing from the `.from` feature.
+Risei's major features are now complete, but new enhancements or fixes may appear from time to time.
 
-Check out the [full list of changes](#version-history).
+The latest release, **3.3.3**, adds `async` capabilities to poly-testing, the last place they were missing.
 
 
 
@@ -123,7 +122,7 @@ tests = [ ...
 ```
 
 - **Asynchronous / awaitable code can tested with no changes at all to this syntax.**
-  - And you use `async` and `await` normally if you define functions within tests.
+  - You use `async` and `await` normally if you define functions within tests.
 - Use empty arrays for `.in` or `.with` when there are no args to pass.
 - You can use [long names](https://deusware.com/risei/index.html#long-names) for properties if you want.
 
@@ -218,56 +217,6 @@ If errors are thrown while testing, gold bars listing them appear at the bottom,
 
 
 
-## Version history
-
-- Release **3.3.2** (September, 2025) contains this change:
-  - You can now use asynchronous / awaitable code in `.from` using `async` and `await` normally.
-    - You already could use awaitable code with the normal syntax in `.plus`, `.do`, and `.undo`.
-
-
-- Release **3.3.1** (February, 2025) contains this change:
-  - You can now spoof and otherwise address value properties (formally _data descriptors_) that don't have an initial value, whether they are static or instance class members.
-
-
-- Release **3.3.0** (January, 2025) adds this change to those of other recent releases:
-  - You can now test instance members with the same names as static members using a new `.and` option of `"instance"`.
-
-
-
-<details>
-<summary>
-Older releases
-</summary>
-
-- Release **3.2.1** (January, 2025) contains all the changes from **3.2.0**, **3.1.1**, and **3.1.0**, plus this change:
-  - Risei's mistaken nominal dependency on **npm** has been removed.
-
-
-- Release **3.2.0** (January, 2025) contains all the changes from **3.1.1** and **3.1.0**, plus this change:
-  - Risei's self-dependency for its own self-testing has been moved back to the development-only scope.
-
-
-- Release **3.1.1** (January, 2025) contains these changes:
-  - Extra commas and non-objects in arrays of test objects are disregarded, and no longer cause a throw.
-  - Throws in wider scopes are now listed at the end, like others already found there.
-
-
-- Release **3.1.0** (January, 2025) contains these changes:
-  - Accessor properties (formally _accessor descriptors_) are now compared for test results and displayed in test outputs.
-    - Any accessor properties that throw errors during display are displayed as `(threw)`.
-  - Throws in tested code and in test framing code are now listed at the end, and also displayed amid the tests.
-  - `File` objects now have a succinct custom display in outputs.
-  - **(Breaking change)**&nbsp;  In `constructor` tests, constructed instances are available in `.from` functions only as `actual` / `test.actual`.
-    - **(Breaking change)**&nbsp;  In `constructor` tests, `test.target` is now the `prototype` of the tested class.
-  - Widespread internal reengineering of other kinds.
-
-
-> Older releases are dropped from this list progressively over time.&nbsp;  Using the latest release is recommended.
-
-</details>
-
-
-
 ## Known issues and workarounds
 
 There are the known minor issues:
@@ -277,10 +226,10 @@ There are the known minor issues:
 
 
 - Spoofing accessor properties only works when they have both a getter and a setter.
-  - The workaround is to find another way to produce the property values you need.
+  - There is no specific workaround for this, but you may look for other ways to produce the property values you need.
 
 
-- Predefined JavaScript methods like `toString()` may not be recognized, nor any instance method that has the same name as a static method.
+- Custom versions of JavaScript methods like `toString()` may not be recognized, nor any instance methods with the same names as static methods.
   - The workaround is to use an `.and` value of `"instance"` for any methods like these that you test.
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "risei",
-  "version": "3.3.2",
+  "version": "3.3.3",
   "description": "Risei allows you to write unit tests as simple JavaScript objects, so it's easy and fast, with no drag on redesign.",
   "keywords": [
     "unit test",
@@ -54,6 +54,6 @@
     "fs": "^0.0.1-security",
     "mocha": "^10.0.0",
     "morgan": "~1.9.1",
-    "risei": "^3.3.1"
+    "risei": "^3.3.2"
   }
 }

package/system/TestTargets.js

@@ -66,11 +66,11 @@ export default class TestTargets {
     // region Dependencies of targeting / naming methods
 
         supplyPolyMethodNonce(test, callable) /* verified */ {
-            let nonce = (...inputs) => {
+            let nonce = async (...inputs) => {
                 let actuals = [];
 
                 for (let args of inputs) {
-                    let local = test.target[callable](...args);
+                    let local = await test.target[callable](...args);
                     actuals.push(local);
                 }