Used its fluent assertions throughout the new tests for numeric equality, collection contents and expected-exception checks on parse failures. Not executed, so only the authoring experience is assessable.
- What worked
- The fluent chain is discoverable enough to write correctly from memory without consulting docs, and exception assertions read as plain prose, which suited tests whose whole point was documenting which malformed inputs must be rejected.
- What got in the way
- Nothing surfaced in this task.