Configuration
Project config lives in taqwright.config.ts. This is what taqwright init generates for an Android project with the demo app, every knob listed, essentials uncommented, the rest commented placeholders you enable by deleting the leading // . The bundled demo app and its managed taqwright_api34 AVD are already wired, so npx taqwright test works out of the box.
Annotations
Annotations let you mark a test as skipped, expected to fail, or slow, tag it for
Command line
taqwright ships a single taqwright binary that runs your tests, scaffolds a project,
Global setup and teardown
Per-test hooks (beforeEach / afterEach, see
Parallelism
taqwright is serial by default, one Appium, one device. To go parallel you either declare a local device pool and raise workers (or let taqwright auto-discover the devices for you), or point at a cloud provider where each worker is its own independent session.
Parameterize tests
You can parameterize tests at two levels: per test, by generating cases from a data
Projects
A project is a named group of tests that run with one use configuration: a platform, a
Reporters
A reporter decides how test results are presented: a live console stream, a browsable HTML
Retries
Retries automatically re-run a failing test a few times before giving up, so an intermittent
Sharding
Sharding splits your test suite into smaller parts, called shards, that run as independent
Timeouts
taqwright has two timeouts you will actually set: the test timeout (how long a whole test may
Actions
Actions drive the app: type into a field, toggle a switch, pick a date, tap a button, swipe a
Assertions
taqwright assertions come in two equivalent styles backed by one engine:
Auto-waiting
Before it drives an element, taqwright runs a short set of actionability checks and retries them
Trace viewer
A taqwright trace is a recording of everything a test did, action by action, that you can replay