Bikeshed recognizes a fake element named for marking "assertions" that tests can refer to. In the generated output, this is converted to a with a unique ID generated from its contents, like issues (described above). This ensures that you have a unique ID that won’t change arbitrarily, but will change when the contents of the assertion change, making it easier to tell when a test might no longer be testing the assertion it points to (because it’s no longer pointing to a valid target at all!).
Wrapping normative statements into assert is not always straightforward, but if we agree on the result, we can then rely on the generated IDs to name test files.
From the Bikeshed documentation:
Wrapping normative statements into assert is not always straightforward, but if we agree on the result, we can then rely on the generated IDs to name test files.
Preview | Diff