The new (cool!) pause() function isn't documented at all in https://codeception.com/docs/modules/WebDriver

I saw the docs at https://codeception.com/docs/02-GettingStarted#Interactive-Pause but it should be explained in the supported modules' docs too!

After the introduction of Public workers API, run-workers can be refracted with the help of this API. This will help us to make enhancements and fixes on workers seamlessly.

Current problem

Gauge's default screenshot tool captures the current display. This does not work on headless environments like CI where tests are run without a display.

It is not clear that a tester can or has to override the default screenshot behaviour

Suggestion

When the default screenshot tool fails to take a screenshot because of the environment add a note or warning i

Hi Jan, so I am successfully able to instantiate Actors from a config block in my setup.ts file like so...

import { setDefaultTimeout } from 'cucumber';
import { Actors } from '../../spec/screenplay/Actors';
import { configure } from '@serenity-js/core';

setDefaultTimeout(10000);

configure({
    actors: new Actors()
});

I instead tried adding actors: new Actors() [with ap

Please take look at ReusingStepDefinitions.md and notice that in the suggested example (second large code block) there is a variable myAccount. However this variable does not exist at this point in time. It seems this shared-steps was created as a result of hasty refactoring, and I see no way to link myAcco

Runner console logs should be logged to the log file when started as daemon.
When gauge is running as lsp server, runner console should be redirected to lsp.log.
When gauge is running as api daemon, runner console should be redirected to api.log.
In the above two cases, runner should log to the log files with proper formatting. Current log file format for gauge is 'HH:MM:ss.l'. (eg :- 12:50:11.221

Right now, tee have an action that runs each test suite one right after the other. However, the test suites are completely independent from each other and so to allow for maximum dev cycles, we should run them in parallel.

Parses a script written in a markdown format to a TestPage
Executes the TestPage by locating the best matching @action within a given @ActionAdapter
Outputs a Value Based Test Execution Report

Actually we support usage of categoryies for tests, but it isn't documented anywhere :(