Detox/docs/api/internals.md

Internals

:::caution

This section might be more volatile than the other ones, yet we'll do our best to adhere to Semantic Release standards even here.

:::

Detox Internals might be useful for developing advanced enterprise presets or if you are planning to integrate with a third-party test runner like Mocha, Ava, Vitest or other ones.

Main lifecycle

resolveConfig

Use with a caution, when you still have no config, yet need to avoid [internals.init()][#init] call.

You normally don't need it if you use Detox CLI (detox test …), but if you want to start tests directly and you need to have the config resolved before [internals.init()][#init] is called, this is the way to go.

getStatus

Returns a string (inactive, init, active or cleanup) depending on what's going on.

init

This is the phase where Detox reads its configuration, starts a server.

cleanup

The global cleanup phase should happen after all the tests have finished. This is the phase where the Detox server shuts down.

installWorker

This is the phase where Detox loads its expectation library and starts a device.

uninstallWorker

Deallocates the device.

Optional lifecycle

Synchronizing with artifacts manager

The naming you can see adheres much to Jest Circus workflow:

• onRunStart
• onRunDescribeStart
• onTestStart
• onHookStart
• onHookFailure
• onHookSuccess
• onTestFnStart
• onTestFnFailure
• onTestFnSuccess
• onTestDone
• onRunDescribeFinish
• onRunFinish

Reporting failed tests

reportFailedTests reports to Detox CLI about failed tests that could have been re-run if --retries is set to a non-zero.

It takes two arguments:

• testFilePaths – array of failed test files' paths
• permanent – whether the failure is permanent, and the tests should not be re-run.
• returns a promise.

Properties

config

session

log

tracing.createEventStream()

Creates a readable stream of the currently recorded events in Chrome Trace Event format.

See also: DurationBeginEvent, DurationEndEvent, InstantEvent.

worker

Not documented on purpose. Provides the direct access to the object which holds the device driver, websocket client, matchers, expectations, etc.