Lippia Test Manager Pytest-BDD Adapter

The Lippia Test Manager adapter allows to ingest pytest-bdd test results into a Lippia Test Manager instance.
To have access to a Lippia Test Manager go to Lippia.io website.

Getting Started

Import dependency

In order to utilize the LTM reporting library, you first need to set the environment variables with the values for LTM-User, LTM-Pass, LTM-HostKey, LTM-RepositoryUrl and LTM-RepositoryBranch. Next, you'll need to add the git line to download the dependency in the requirements file with "git+ssh://git@ssh....../pytest-bdd-7-adapter.git". Lastly, set the values for the Project code and Run name variables in the config.py file.

The implementation of the Lippia Test Manager reporter requires the use of hooks by implementing the TestManagerAPIAdapter class in the conftest.py file

git+ssh://git@ssh....../pytest-bdd-7-adapter.git

Report Class

The TestManagerAPIAdapter class defines a set of methods to interact with the Lippia Test Manager API and record information about Pytest BDD scenarios and steps.

To implement the adapter, it is necessary to create the conftest.py file; import and initialize the TestManagerAPIAdapter and TestManagerAPIClient classes, followed by the invocation of the hooks belonging to pytest-bdd

Initialize the TestManagerAPIClient

TestManagerAPIClient.initialize_rest_template(RUN_NAME=config.RUN_NAME, PROJECT_CODE=config.PROJECT_CODE)

Instantiate the TestManagerAPIAdapter

adapter_instance = TestManagerAPIAdapter()

Define your Pytest BDD hooks to use the adapter

def pytest_bdd_after_scenario(feature, scenario):
adapter_instance.pytest_bdd_after_scenario(feature, scenario)

def pytest_bdd_after_step(step, step_func_args):
adapter_instance.pytest_bdd_after_step(step, step_func_args)

def pytest_bdd_step_error(step, exception):
adapter_instance.pytest_bdd_step_error(step, exception)

When running the tests, the hooks in the conftest file will automatically execute, injecting the generated report into LTM.

Configure the env variables

Key	Concept	Is
TEST_MANAGER_USER_KEY	User with which the Test Manager instance will be authenticated	Mandatory
TEST_MANAGER_PASS_KEY	Password with which the Test Manager instance will be authenticated	Mandatory
TEST_MANAGER_API_HOST_KEY	Host to which the adapter will attempt to authenticate	Mandatory
TEST_MANAGER_API_PORT_KEY	Port on which the Test Manager instance will be listening	Optional
TEST_MANAGER_REPOSITORY_URL	URL of the repository linked to the project	Mandatory
TEST_MANAGER_REPOSITORY_BRANCH	Branch from where the automated tests are being injected	Mandatory

Local variables in the config file

Key	Concept	Is
RUN_NAME	Run name, serves as identifier of the suite execution	Mandatory
PROJECT_CODE	Project Code into which the adapter will attempt to inject test results	Mandatory