Features

This section describes all features that are shipped with this package.

Scenario Features

Main Features

class balderhub.textual.lib.scenario_features.AppFeature(**kwargs)

Bases: Feature

Basic feature that provides the textual app instance that should be tested.

get_app() → App

Returns the app instance that should be tested.

class balderhub.textual.lib.scenario_features.TextualControlFeature(**kwargs)

Bases: GuiControlFeature

Feature to control a textual application - necessary to interact with a textual application.

class App

Bases: VDevice

the app vdevice that provides the app instance under test

create() → None

creates the driver class to control the app - needs to be called within a fixture

property driver: TextualDriverClass

Returns:

returns the base driver class (holds the custom implementation of the guicontrol tool)

Page Object Model Feature

class balderhub.textual.lib.scenario_features.TextualPage(**kwargs)

Bases: PageFeature

Page object for textual application screens

property applicable_on_screen_id: str

Should return the screen id - is used to determine which screen is active at the moment

property driver: TextualDriverClass

Returns the driver instance

is_applicable()

Returns true if the current screen is the expected one (see TextualPage.applicable_on_screen_id())

wait_till_applicable(timeout=5)

Waits until the expected screen is active (default timeout is 5 seconds)

Setup Features

Note

This BalderHub project doesn’t have any setup features.