mirror of
https://github.com/Permissionless-Software-Foundation/psf-memo.git
synced 2026-09-21 16:52:01 -07:00
Chris Troutner
3f05488da0
- Add DB unit tests covering a summary missing postCount, a post missing blockHeight in listTopics/getTopicPostTxids ordering, listTopics' default limit/offset, and topicRecencyKey's missing-height fallback. These kill the remaining language-mutation survivors in the changed DB sources. - Refresh the mutate4javascript manifests for the changed sources and commit the gherkin-mutator manifests/stamps written into the three topic-metadata features. - No production behavior changes; the review adds tests and tool-written metadata only. By architect.
90 lines
5.9 KiB
Gherkin
90 lines
5.9 KiB
Gherkin
# mutation-stamp: sha256=a7af9fed2e6666ad93c80887c4e0a99aa3e228da6eb00c46f30e1ffbbd3825e6
|
|
# acceptance-mutation-manifest-begin
|
|
# {"version":1,"tested_at":"2026-09-18T13:25:05.913631022Z","feature_name":"Topic Metadata","feature_path":"/home/trout/work/psf-memo/.worktrees/architect/psf-memo-db/specs/topic-metadata.feature","background_hash":"622a318a0cc0b3d885a9951ae6f22a74f37e4e7842ebfb6a6d9cffe0b0dcce85","implementation_hash":"unknown","scenarios":[{"index":0,"name":"Topic Metadata - 1 GET /topics returns each topic's last-seen time","scenario_hash":"cbdac93ce1eb89a953548fe391593d674f843d5efa6b27042ae030763e50ff10","mutation_count":6,"result":{"Total":6,"Killed":6,"Survived":0,"Errors":0},"tested_at":"2026-09-18T13:25:05.913631022Z"},{"index":1,"name":"Topic Metadata - 2 GET /topics returns each topic's follower count","scenario_hash":"0ccdf1b954eb4787b9075a63d2bcb0aeb6da90243b7670c712ef1de7cffc6542","mutation_count":6,"result":{"Total":6,"Killed":6,"Survived":0,"Errors":0},"tested_at":"2026-09-18T13:25:05.913631022Z"},{"index":2,"name":"Topic Metadata - 3 backfill records each room's last-seen time","scenario_hash":"094bdaa1176c9a2c2aca6e46b4853e512cf140e77999cc6fb696fdbeda2402f3","mutation_count":6,"result":{"Total":6,"Killed":6,"Survived":0,"Errors":0},"tested_at":"2026-09-18T13:25:05.913631022Z"},{"index":3,"name":"Topic Metadata - 4 backfill records each room's follower count","scenario_hash":"80ac7a2c4143421b9268c05c1f5f83d3f5335c9cd6ad1edc70b85c76e9afe683","mutation_count":6,"result":{"Total":6,"Killed":6,"Survived":0,"Errors":0},"tested_at":"2026-09-18T13:25:05.913631022Z"},{"index":4,"name":"Topic Metadata - 5 backfill is idempotent for topic metadata","scenario_hash":"d3f7f226124160e334e8547e4c05c020bdd66acac0445155de93c6615299cacf","mutation_count":6,"result":{"Total":6,"Killed":6,"Survived":0,"Errors":0},"tested_at":"2026-09-18T13:25:05.913631022Z"}]}
|
|
# acceptance-mutation-manifest-end
|
|
|
|
# Scenarios: Topic Metadata - 1, Topic Metadata - 2, Topic Metadata - 3, Topic Metadata - 4, Topic Metadata - 5
|
|
#
|
|
# GET /topics reports each topic's lastSeen (the epoch-millisecond time of the
|
|
# room's most recent post, 0 for a follow-only room) and followerCount (the
|
|
# number of active follows) alongside the existing postCount. The topic
|
|
# backfill utility rebuilds lastSeen and followerCount from the rooms store, and
|
|
# running it twice is idempotent.
|
|
#
|
|
# Fixture "topic-metadata-indexes" (topic index stores):
|
|
# topicSummaries:
|
|
# memo { room: memo, postCount: 5, lastHeight: 600500, lastSeen: 1700020000000, followerCount: 12 }
|
|
# cash { room: cash, postCount: 2, lastHeight: 600400, lastSeen: 1700010000000, followerCount: 4 }
|
|
# lone { room: lone, postCount: 0, lastHeight: 0, lastSeen: 0, followerCount: 7 }
|
|
# topicRecency:
|
|
# memo at 600500, cash at 600400, lone at 0
|
|
#
|
|
# Fixture "rooms-with-topic-metadata" (rooms store):
|
|
# bitcoin:post-100 { room: bitcoin, txid: post-100, type: post, blockHeight: 600100, seen: 1700000000000 }
|
|
# bitcoin:post-200 { room: bitcoin, txid: post-200, type: post, blockHeight: 600200, seen: 1700009999000 }
|
|
# bitcoin:addr-f { room: bitcoin, addr: bitcoincash:qaddr-f, type: follow, unfollow: false }
|
|
# bitcoin:addr-g { room: bitcoin, addr: bitcoincash:qaddr-g, type: follow, unfollow: false }
|
|
# cash:post-250 { room: cash, txid: post-250, type: post, blockHeight: 600250, seen: 1700012345000 }
|
|
# cash:addr-f { room: cash, addr: bitcoincash:qaddr-f, type: follow, unfollow: true }
|
|
# lone:addr-f { room: lone, addr: bitcoincash:qaddr-f, type: follow, unfollow: false }
|
|
Feature: Topic Metadata
|
|
|
|
Background:
|
|
Given a psf-memo-db instance with rooms, topicSummaries, and topicRecency stores
|
|
|
|
Scenario Outline: Topic Metadata - 1 GET /topics returns each topic's last-seen time
|
|
Given the fixture "topic-metadata-indexes" is loaded into the topic index stores
|
|
When the client requests /topics
|
|
Then the response contains the topic "<topic>" last seen at <lastSeen>
|
|
|
|
Examples:
|
|
| topic | lastSeen |
|
|
| memo | 1700020000000 |
|
|
| cash | 1700010000000 |
|
|
| lone | 0 |
|
|
|
|
Scenario Outline: Topic Metadata - 2 GET /topics returns each topic's follower count
|
|
Given the fixture "topic-metadata-indexes" is loaded into the topic index stores
|
|
When the client requests /topics
|
|
Then the response contains the topic "<topic>" with <followerCount> followers
|
|
|
|
Examples:
|
|
| topic | followerCount |
|
|
| memo | 12 |
|
|
| cash | 4 |
|
|
| lone | 7 |
|
|
|
|
Scenario Outline: Topic Metadata - 3 backfill records each room's last-seen time
|
|
Given the fixture "rooms-with-topic-metadata" is loaded into the rooms store
|
|
When the topic backfill utility is run
|
|
Then the topicSummaries store records the room "<room>" last seen at <lastSeen>
|
|
|
|
Examples:
|
|
| room | lastSeen |
|
|
| bitcoin | 1700009999000 |
|
|
| cash | 1700012345000 |
|
|
| lone | 0 |
|
|
|
|
Scenario Outline: Topic Metadata - 4 backfill records each room's follower count
|
|
Given the fixture "rooms-with-topic-metadata" is loaded into the rooms store
|
|
When the topic backfill utility is run
|
|
Then the topicSummaries store records the room "<room>" with <followerCount> followers
|
|
|
|
Examples:
|
|
| room | followerCount |
|
|
| bitcoin | 2 |
|
|
| cash | 0 |
|
|
| lone | 1 |
|
|
|
|
Scenario Outline: Topic Metadata - 5 backfill is idempotent for topic metadata
|
|
Given the fixture "rooms-with-topic-metadata" is loaded into the rooms store
|
|
When the topic backfill utility is run
|
|
And the topic backfill utility is run again
|
|
Then the topicSummaries store records the room "<room>" last seen at <lastSeen>
|
|
And the topicSummaries store records the room "<room>" with <followerCount> followers
|
|
|
|
Examples:
|
|
| room | lastSeen | followerCount |
|
|
| bitcoin | 1700009999000 | 2 |
|
|
| lone | 0 | 1 |
|