Cookiebot
Progress

Scenario ledger

Every Gherkin spec file — written in v1's QA repo, ported to v2, executing green

The v1 QA repository holds the intended behaviour as Gherkin. None of it was executable: 63 scenarios describing a bot, run by nobody. Porting a feature means making its scenarios run against v2 — same wording, real assertions.

This ledger is the honest version of "how much of the spec do we actually execute". A row with scenarios written and none ported is work not started; a row that is green is behaviour that would break the build if it regressed.

Specv1PortedGreenFailingState
core_botskins355—green
core_groupguardian299—green
core_listcommand246—green
core_llm_provider—99—v2-only spec
core_media_storage—88—v2-only spec
core_mediarestrict269—green
core_musicdetection155—green
core_privacy148—green
core_reload—23—v2-only spec
core_rules4914—green
core_setlang388—green
core_stickerspam269—green
core_welcome31018—green
fun_battle11010—green
fun_complaint244—green
fun_death278—green
fun_dice389—green
fun_firecracker122—green
fun_meme244—green
fun_partneredcons71010—green
fun_random1533—green
fun_ship378—green
util_birthday133—green
util_calladms147—green
util_config256—green
util_deletereposts222—green
util_doomlist164—green
util_embedder2916—green
util_everyone233—green
util_isalive244—green
util_nextbirthday122—green
util_postforwarder288—green
util_postgetter144—green
util_youtube111—green
x_age_guess—57—v2-only spec
x_analysis—47—v2-only spec
x_conversational_ai—77—v2-only spec
x_custom_commands—66—v2-only spec
x_distortion—1012—v2-only spec
x_drawing_idea—35—v2-only spec
x_fortune_cookie—35—v2-only spec
x_gender_guess—68—v2-only spec
x_giveaways—1010—v2-only spec
x_image_search—1010—v2-only spec
x_owner_commands—89—v2-only spec
x_reverse_search—66—v2-only spec
x_speech_to_text—66—v2-only spec
x_sticker_autoreply—66—v2-only spec
x_unearth—56—v2-only spec

Reading a state

StateMeans
greenEvery ported scenario for this spec executed and passed
partialSome of the v1 scenarios are ported, others are not
not portedv1 specified it; v2 has no executable scenario yet
v2-only specBehaviour v2 added or pinned down that v1 never specified
failingA ported scenario is red — the one state that is a bug, not a plan
no step definitionsThe .feature file exists but nothing binds its steps

On this page