Repository navigation
Commit 95221ec
committed
docs(ofrep): correct two tallies that reason.feature left behind
Running the suite to confirm this pass moved nothing found a count that had
already moved and not been written down. `poe test-tck` is 2 failed, 45 passed,
17 skipped, 1 xfailed; `pyproject.toml` still said 2 / 37 / 16 / 1, which was
true when this suite collected 56 scenarios and stopped being true when
reason.feature took it to 65. The README already carried the right figure, so
the two disagreed with each other as well as with the run.
The @disabled-flags note quoted the same superseded run as its measurement of
what declaring the tag would cost. The measurement stands -- all four rows fail,
on the error code rather than the value -- so it is kept and dated rather than
rewritten, with today's baseline beside it and the arithmetic said plainly:
the same four rows move from skipped to failed.
Same lesson as the three stale tallies the flagd suite carried a pass ago. A
count in prose is a claim, it ages the moment the assets move, and the only
thing that finds it is running the suite and comparing.
Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>1 parent 82d6642 commit 95221ec
2 files changed
Lines changed: 7 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
85 | 85 | | |
86 | 86 | | |
87 | 87 | | |
88 | | - | |
| 88 | + | |
89 | 89 | | |
90 | 90 | | |
91 | 91 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
163 | 163 | | |
164 | 164 | | |
165 | 165 | | |
166 | | - | |
167 | | - | |
168 | | - | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
| 169 | + | |
| 170 | + | |
| 171 | + | |
169 | 172 | | |
170 | 173 | | |
171 | 174 | | |
| |||
0 commit comments