Skip to content
TSMC

Demo mode

Окно терминала
pnpm build
pnpm demo            # http://127.0.0.1:3000 with demo data in data/demo.db (the working database is untouched)
pnpm demo --reset    # start from a clean demo
docker run --rm -p 3000:3000 -e TSMC_DEMO=1 tsmc   # the same in Docker; data lives until the container stops

The demo fills an empty database only. The sign-in page lists five accounts (administrator, editor, two testers, viewer; password demo1234), and the header shows a “Demo” badge. The data:

  • Online shop — 37 cases in a suite tree with code patterns; 11 regression runs over 4 months by two testers, 12 nightly imports of automated tests from CI, and a current regression in progress with assignees. Findings for hygiene are planted on purpose (2 pairs of duplicates, a case not run for long, one that never fails, a flaky automated test), and “Refund” was broken recently — “Pick by changes” puts it first for the file src/payments/refund_service.ts. The runs are filed under the sprints “Спринт 22” (the last one) and “Спринт 23” (the current one); there is also the milestone “Релиз 3.1”.
  • TSMC (this project) — manual cases for the key scenarios and a real vitest JUnit report with 118 automated tests of TSMC itself.

The history is built back from today’s date and is the same every time. Do not set TSMC_DEMO on a production server: the demo users’ passwords are shown to everyone on the sign-in page.

For demo data on a server others reach (a team stand), use TSMC_DEMO_DATA=1 with TSMC_ADMIN_EMAIL and TSMC_ADMIN_PASSWORD instead: an empty database gets the same projects and history, the demo accounts are locked (they stay as authors), and the administrator is the one from the environment. TSMC_STAND_COMMIT and TSMC_STAND_BUILT_AT put a “Stand · commit” badge in the header. See A team stand on your own computer.