TestFlows is overengineered

[alexey-milovidov]

Example:

$ find . -name requirements.md | xargs grep -F 'version: ' | uniq -c
    210 ./aes_encryption/requirements/requirements.md:version: 1.0
     65 ./ldap/authentication/requirements/requirements.md:version: 1.0
     28 ./ldap/external_user_directory/requirements/requirements.md:version: 1.0
      1 ./ldap/external_user_directory/requirements/requirements.md:version: 2.0
     38 ./ldap/external_user_directory/requirements/requirements.md:version: 1.0
      1 ./ldap/external_user_directory/requirements/requirements.md:version: 2.0
     17 ./ldap/external_user_directory/requirements/requirements.md:version: 1.0
    498 ./rbac/requirements/requirements.md:version: 1.0

It contains version specification for every requirement.
Developer should not maintain these version numbers, they would better to be generated automatically from VCS or (better) do not exist.

[alexey-milovidov]

"Requirements" looks like they are designed only to be printed and to waste paper.

[vzakaznikov]

Each requirement needs a version to keep track when the requirement changes so that tests that are linked to it fail when version mismatches. We can't rely on the VCS for versioning as that would not be feasible inside a single document.
There is minimal burden in maintaining versions for each requirement as developer simply increments the version number when material changes to the requirement is made. This feature is critical as it allows for natural process of software evolution.

[vzakaznikov]

"Requirements" looks like they are designed only to be printed and to waste paper.

The main purpose of the requirements is to formalize software functionality and provide the insight into the functional test coverage. It is a critical part of any software development :).

[vzakaznikov]

An example of updated requirements can be found at ClickHouse/ClickHouse#18221.,