tikolakin / pytestomatio

Pytest plugin to analyze tests and link them automatically with Testomat.io test case management system

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Support Ukraine Badge

testomat.io plugin for pytest

uses testomat.io API:

Installation

pip install git+https://github.com/tikolakin/pytestomatio.git@1.7#egg=pytestomatio

configuration

Create environment variable TESTOMATIO and set your testomat.io API key. Linux:

export TESTOMATIO=<key>

Windows (cmd):

set TESTOMATIO=<key>

Run groups parameter

There is environment variable TESTOMATIO_RUNGROUP_TITLE that can be used to specify run tests with specific group title.

pytest.ini

In case you are using private testomat.io service, create pytest.ini file in your project root directory. Specify testomat.io url in it

[pytest]
testomatio_url = https://app.testomat.io

Usage

Synchronize tests to testomat.io and get back test id. Tests will not be executed

pytest --testomatio sync

Remove all test ids from source code. Tests will not be executed

pytest --testomatio remove

Run pytest and send test results into testomat.io.
Test can be sent to testomat.io without ids in your test code. If testomat.io failed to match tests by title, it will create new tests for the run

pytest --testomatio report

Run pytest with debug parameter to get test data collected in metadata.json file

pytest --testomatio debug

Submitting Test Run Environment

to configure test environment, you can use additional option:

pytest --testomatio report --testRunEnv "windows11,chrome,1920x1080"

Environment values are comma separated, please use double quotation.

Submitting Test Artifacts

testomat.io does not store any screenshots, logs or other artifacts.

In order to manage them it is advised to use S3 Buckets (GCP Storage). https://docs.testomat.io/usage/test-artifacts/

Analyser needs to be aware of the cloud storage credentials. There are two options:

  1. Enable Share credentials with testomat.io Reporter option in testomat.io Settings -> Artifacts.
  2. Use environment variables ACCESS_KEY_ID, SECRET_ACCESS_KEY, ENDPOINT, BUCKET

You would need to decide when you want to upload your test artifacts to cloud storage

  1. Upload page screenshot when test fails, using fixtures reference
# content of conftest.py
import pytest
from typing import Dict
from pytest import StashKey, CollectReport
from playwright.sync_api import Page

phase_report_key = StashKey[Dict[str, CollectReport]]()

@pytest.hookimpl(wrapper=True, tryfirst=True)
def pytest_runtest_makereport(item, call):
    rep = yield
    item.stash.setdefault(phase_report_key, {})[rep.when] = rep
    return rep


@pytest.fixture(scope="function")
def handle_artifacts(page: Page, request):
    yield
    report = request.node.stash[phase_report_key]
    if ("call" not in report) or report["setup"].failed or report["call"].failed:
        random_string = ''.join(random.choices(string.ascii_letters + string.digits, k=8))

        filename = f"{random_string}.png"
        screenshot_path = os.path.join(artifacts_dir, filename)
        page.screenshot(path=screenshot_path)
        # file_path - required, path to file to be uploaded
        # file_bytes - required, bytes of the file to be uploaded
        # key - required, file name in the s3 bucket
        # bucket_name - optional,name of the bucket to upload file to. Default value is taken from testomat.io
        artifact_url = pytest.testomatio.upload_file(screenshot_path, filename)
        # or
        # artifact_url = pytest.testomatio.upload_file_object(file_bytes, key, bucket_name)
        pytest.testomatio.add_artifacts(request.node, [artifact_url])
    page.close()

⚠️ Please take into account s3_connector available only after pytest_collection_modifyitems() hook is executed.

  1. If you prefer to use pytest hooks - add pytest_runtest_makereport hook in your conftest.py file.
def pytest_runtest_makereport(item, call):
    artifact_url = pytest.testomatio.upload_file(screenshot_path, filename)
    pytest.testomatio.add_artifacts([artifact_url])

Clarifications

  • tests can be synced even without @patest.mark.testomatio('@T96c700e6') decorator.
  • test title in testomat.io == test name in pytest
  • test suit title in testomat.io == test file name in pytest

Example of test

To make the experience more consistent, it uses standard pytest markers.
testomat.io test id is a string value that starts with @T and has 8 symbols after.

import pytest


@pytest.mark.testomatio('@T96c700e6')
def test_example():
    assert 2 + 2 == 4

Compatibility table with Testomatio check-tests

Action Compatibility Method
Importing test into testomat.io complete pytest --testomatio sync
Exclude hook code of a test N/A N/A
Include line number code of a test N/A N/A
Import Parametrized Tests complete default behaviour
Disable Detached Tests complete pytest --testomatio sync --no-detached
Synchronous Import complete default behaviour
Auto-assign Test IDs in Source Code complete default behaviour
Keep Test IDs Between Projects complete pytest --testomatio sync --create
Clean Test IDs complete pytest --testomatio remove
Import Into a Branch N/A N/A
Keep Structure of Source Code complete pytest --testomatio sync --keep-structure
Delete Empty Suites complete pytest --testomatio sync --no-empty
Import Into a Specific Folder complete pytest --testomatio --directory "Windows\smoke"
Debugging parity pytest --testomatio debug

Change log

2.1.0

  • Added support for TESTOMATIO_TITLE, TESTOMATIO_SHARED_RUN and TESTOMATIO_LABEL

2.0.0 - Reunion

  • Align naming with Testomat.io branding
  • add --directory option to import test into specific directory in testomat.io

1.7.0 - Fixes parameterized test sync and report

1.6.0 - Fixes nested suites

  • Testomaito not longer supports nested test suites. Suites could be only in a folder.
  • Add helped to attach test artifacts
  • Expose environment variables to provide access to cloud storage
  • Update readme

1.5.0 - Fixes artifacts in fixtures lifecycle

  • Earlier, artifacts added in pytest fixtures where scipped by analyser

1.4.0 - Fixes artifacts and test sync with Testomatio

  • Fixes artifacts uploads
  • Fixes test id resolution when syncing local test with Testomatio
  • Fixes test id when sending test into test run
  • Adds --create, --no-detached, --keep-structure, --no-empty, for compatibility with original Testomatio check-tests
  • Improves file update so it doesn't cause code style changes

1.3.0 - added artifacts support connector

  • issue 5 - connection issues not blocking test execution anymore

1.2.8 - fixed issues

  • issue 4 - Analyzer's execution order

1.2.5 - fixed issues

  • added env variable TESTOMATIO_RUNGROUP_TITLE to group test runs
  • fixed serialization issue for update test status example

1.2.4 - improved parametrized tests reporting

  • now parameters are passed to example attribute in the report

1.2.3 - fixed issue with test artifacts

  • if no credentials provided, test artifacts will not be uploaded and no issue raised

1.2.0 - major update after testomat.io review

  • code refactored
  • simplified authentication. Only API key needed
  • moved API key from pytest.ini to environment variable
  • S3 credentials now read from testomat.io API, no local configuration needed
  • Prettified test names in testomat.io

1.1.0 - added artifacts support connector

  • there is possibility to add artifacts (screenshots, logs) to test report

1.0.9 - first public release

  • test analyzer able to sync tests with testomat.io
  • test analyzer able to add test ids to tests
  • test analyzer able to submit test results to testomat.io

Test

  • import into empty project
  • updated test - (resync)
  • test run
  • test run into a folder
  • test run labels, tags

TODO

  • Fix test duration
  • Require more back references from testomatio
  • pytest.skip should behave as @pytest.mark.skip

About

Pytest plugin to analyze tests and link them automatically with Testomat.io test case management system

License:MIT License


Languages

Language:Python 100.0%