Repository navigation
Commit a921b7a
committed
test(flagd): the falsy flags were a naming gap, not a backend gap
The suite's note on what flagd-testbed does not serve was written against
spec@15fe8611 and listed six missing flags. Three of them were never missing.
spec@ba002ce8 renames them to boolean-zero-flag, integer-zero-flag and
string-zero-flag, which is what flagd-testbed's own flags/zero-flags.json has
called them all along, with the same zero/non-zero variants the scenarios
assert. Verified against flagd-testbed v3.8.0: all three resolve with variant
zero and reason STATIC on both resolvers.
What remains genuinely unseeded is large-integer-flag, huge-integer-flag and
integral-float-flag, so the note now names those three and lists only the two
scenarios that still fail. The reasoning underneath is unchanged: the failures
stay failures rather than xfails, because they say something true about the
backend rather than about the provider.
Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>1 parent 8622d89 commit a921b7a
1 file changed
Lines changed: 12 additions & 8 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
14 | 14 | | |
15 | 15 | | |
16 | 16 | | |
17 | | - | |
18 | | - | |
19 | | - | |
20 | | - | |
21 | | - | |
22 | | - | |
23 | | - | |
24 | | - | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
25 | 23 | | |
26 | 24 | | |
27 | 25 | | |
| |||
31 | 29 | | |
32 | 30 | | |
33 | 31 | | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
34 | 38 | | |
35 | 39 | | |
36 | 40 | | |
| |||
0 commit comments