Test::Async::TestTool
- role consumed by test tool methods
This role is applied by test-tool
trait to a test tool method.
Contains the name which must be used for exporting a test tool routine. Makes sense if method must be named differently from what is provided for the user.
Bool:D
$.readify
This flag is indicating if test tool must cause it's suite object to transition from TSInitializing
stage.
Bool:D
$.skippable
This flag indicates that this test tool could be skipped. A typical example of a non-skippable tool is the skip
itself, or todo
tool family. The importance of this nuance stems from the fact that when skip-remaining
tool is in effect the wrapper of a test tool code detects this situation and emits a skip event instantly without actually invoking the tool method. Without $.skippable
reset to False a line like:
skip "for a reason", 3 would result in a single skip event which is counted as a test run. Our plan will fail because of 2 missing skip events.
Bool:D
$.wrappable
Resetting this flag to False would result in test tool method would be left intact by Test::Async::Metamodel::BundleClassHOW
.
Bool:D
$.anchoring
Marks a test tool as an anchoring one. See Test::Async::Manual
Call Location And Anchoring section for more details.
False by default.
Sets $.tool-name
.
Sets $.readify
Sets $.skippable
Sets $.wrappable
(c) 2020-2023, Vadim Belman [email protected]
Artistic License 2.0
See the LICENSE file in this distribution.