Skip to content

usertest: synthetic sample data for sessions that shouldn't need a real account (money first) #196

Closed

Description

@michielbdejong

Problem

The money session plan (usertest/moderator/sessions/money.md, #193) needs a tester's own MT940 or camt.053 bank export. That puts real transactions on a screen that is recorded, sent to Anthropic's API for the analysis and kept on the droplet. Many testers will rightly say no and skip the session, so the Money app gets hardly any sessions.

Proposal: a synthetic sample statement

  • Serve one or two synthetic statements from the catalog host, e.g. https://catalog.<base-domain>/samples/money/statement.mt940 and a camt.053 version. usertest/catalog.mjs would copy them into out/samples/, and deploy.sh would ship samples with catalog.json apps.
  • Build them from integrations/money/fixtures/, extended to about 30–60 transactions over two months:
    • an invented account ("Acme Studio", NL00 BANK 0000 0000 00) and invented counterparties
    • one refund, one foreign-currency payment, one long bank description
    • an overlapping second file for the "import again" task
  • The page (usertest/page/) shows a download link when the invite link has session=money. The moderator can't speak URLs, so it would say "use the sample statement on the session page".
  • In money.md: offer the sample first and the tester's own export as an option, and drop the privacy question from the first turn.

Wider: sample data where a real account isn't needed

"We'll see", but the same idea applies elsewhere:

  • GitHub: point testers at a disposable sandbox repository, e.g. ontola/usertest-sandbox, with a set of invented issues, labels and comments. Testers connect their real GitHub account (the real OAuth and proxy path is what we want to test), but nobody has to use a real issue tracker, and "close an issue" or "report a new bug" can't bother anyone. It needs a decision on who may write to it: a public repo where any GitHub user can open issues, or a collaborator invite per tester. Also a reset script to restore the seeded issues between sessions.
  • Clockify and Notion: there's no shared sandbox, since testers need their own workspace. A short "create these three entries / this small database first" preparation step could replace an empty account.
  • Calendar: a public sample .ics or a shared test calendar would let testers skip their personal calendar.

Each of these changes the matching plan in usertest/moderator/sessions/ (its skip path and its first task).

Done when

  • A synthetic MT940 and camt.053 are served from the catalog host and linked from the session page for session=money
  • money.md uses them
  • A decision on the GitHub sandbox repository (and the other providers), recorded here or in follow-up issues

Activity

  1. added a commit that references this issue on Oct 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions