taler-monitoring: shop e2e uses catalog list and random pick of two

The GOA shop e2e path used to walk every product template every run, which
was slow and often hit balance or time budgets after the first few pays.

Keep the full catalog in E2E_SHOP_PRODUCTS (id|name|amount, synced with the
merchant landing). Each e2e run shuffles that list and pays only
E2E_SHOP_PICK_N products (default 2). Shop pays pin instance goa-shop for
public template POSTs; settlement payto matches the landing shop popup.

Docs in README.md and TESTS.md describe the pick behaviour and env overrides.
This commit is contained in:
Hernâni Marques 2026-07-10 20:28:15 +02:00
parent c7f86dd3da
commit 04bafc84a6
No known key found for this signature in database
3 changed files with 83 additions and 44 deletions

View file

@ -61,9 +61,10 @@ Other domains: never SSH. Optional **e2e** aborts cleanly on login/KYC.
# customize:
E2E_WITHDRAW_VALUES="20 50 100" E2E_PAY_VALUES="0.05 1 5" ./taler-monitoring.sh e2e
E2E_VARIABLE=0 WITHDRAW_AMT=GOA:50 PAY_AMT=GOA:1 ./taler-monitoring.sh e2e # single fixed
# GOA shop catalog (local hacktivism): public template POST + wallet pay per product
# GOA shop catalog (local hacktivism): full list in E2E_SHOP_PRODUCTS; each run
# shuffles and pays E2E_SHOP_PICK_N products (default 2).
# E2E_SHOP_PRODUCTS lines: id|Product name|GOA:amount
# E2E_SHOP_PRODUCTS=$'orbit-sticker|Orbit sticker pack|GOA:2\nnebula-coffee|Nebula coffee|GOA:5'
# E2E_SHOP_PICK_N=2
# (landing QR = taler://pay-template/…/{id}; popup = live taler://pay after POST templates/{id})
# remote secrets:
# E2E_BANK_ADMIN_PASS=… E2E_MERCHANT_TOKEN=…