---
title: "Comment by QRiQRa Team on \"Specs as Laws\" | Hashnode"
description: "The useful move is to read a Given, When and Then example as a law with its quantifiers hidden: one reading and one share stand in for every reading and every s"
url: "https://hashnode.com/posts/specs-as-laws/6b010e55937f3f6d0d4698e3/comment/6b011f78b869cb5640fc199b"
---

[Discussion](https://hashnode.com/posts/specs-as-laws/6b010e55937f3f6d0d4698e3)

Comment [Specs as Laws](https://hashnode.com/posts/specs-as-laws/6b010e55937f3f6d0d4698e3)

[QRiQRa Team](https://hashnode.com/@qriqra)

[16h ago](https://hashnode.com/posts/specs-as-laws/6b010e55937f3f6d0d4698e3/comment/6b011f78b869cb5640fc199b)

The useful move is to read a Given, When and Then example as a law with its quantifiers hidden: one reading and one share stand in for every reading and every share. That turns the check into generating many inputs and testing the law on each, rather than stopping at the example. Writing the checker from scratch, with a named seed so a failure can be replayed on any machine, keeps that path in view. The closing point is fair: property tests are evidence, never proof, and when theory and practice disagree, finding out which is wrong is the most useful thing a test can do.
