Configuration file

ℹ️ Available since Steward 2.2.

Configuration file is useful for a static global configuration that doesn't change for different tests runs.

Usage

Place steward.yml or steward.yml.dist file to your base directory, or use -c/--configuration runtime option to define a custom path to the configuration file.

Supported options

Option	Description	Example
`capabilities_resolver`	Custom capabilities resolver class (must implement `CapabilitiesResolverInterface`). This is useful when `--capability` CLI option (see docs) is not enough for you or you use the same capabilities each run - you can simply implement custom class to resolve capabilities based on any logic you want. See wiki page for more information.	`My\Steward\CustomCapabilitiesResolver`
`tests_dir`	Path to directory with tests. Similar to `--tests-dir` CLI option (which could also be used to override the value from config file).	`./tests`
`logs_dir`	Path to directory with tests. Similar to `--logs-dir` CLI option (which could also be used to override the value from config file).	`/tmp/logs`
`fixtures_dir` ℹ️ Removed in Steward 3.0.	Path to directory with tests. Similar to `--fixtures-dir` CLI option (which could also be used to override the value from config file).	`/tmp/fixtures`

Example

# steward.yml
tests_dir: selenium-tests/
logs_dir: /tmp/logs
capabilities_resolver: My\Steward\CustomCapabilitiesResolver

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Configuration file

Usage

Supported options

Example

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Clone this wiki locally