Skip to content

TESTING.md

Latest commit

 

History

History
47 lines (37 loc) · 1.27 KB

TESTING.md

File metadata and controls

47 lines (37 loc) · 1.27 KB
Raw

Unit Frontend

The web UI lives in res/app/src (React + TypeScript). Its specs sit next to the code as *.test.ts(x) and run with Vitest in jsdom, no browser needed:

npm run test:component

Type checking and linting of the UI are part of npm run lint (node build.mts lint runs eslint and tsc -p res/app/tsconfig.json).

E2E Frontend

The end-to-end suite is Playwright, in test/playwright. It drives a running stf local through a real Chromium.

  • Run RethinkDB 
      rethinkdb
  • Compile lib/ and run stf with mock auth 
      node build.mts compile
  ./bin/stf local --auth-type mock
    Wait till STF is fully functional and devices are discovered
  • Install and run the suite 
      cd test/playwright
  npm install && npx playwright install chromium
  npx playwright test ui.spec.ts
  STF_DEVICE_SERIAL=emulator-5554 npx playwright test

ui.spec.ts needs no device. device.spec.ts skips itself unless STF_DEVICE_SERIAL names a connected device.

Results land in test-results/playwright (an HTML report under html/, traces and videos under artifacts/).

Remote STF

  • export STF_URL='http://stf-url/'
  • export STF_USERNAME='user'
  • export STF_EMAIL='user@example.com'
  • cd test/playwright && npx playwright test