testeiya 0.2.1 → 0.3.9

package/skills/testeiya/testomatio-docs/docs/test-reporting/pipes/html.md

@@ -1,80 +0,0 @@
----
-title: HTML
-description: Discover how to use Testomat.io's HTML Pipe to generate detailed HTML reports from your test runs. Learn how to configure environment variables to save reports, customize output paths, and view essential test data like execution time and status.
-type: article
-url: https://docs.testomat.io/test-reporting/pipes/html
-head:   
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, HTML reports, test reporting, test automation, environment variables, CI/CD, CodeceptJS, test result visualization, report generation
----
-## Testomat.io HTML Pipe
-
-The Testomat.io HTML Pipe is a feature that allows you to generate and save HTML reports based on your test results. This functionality is part of the Testomat.io testing ecosystem.
-
-### Prerequisites
-
-**🔌 TESTOMATIO users now have the option to generate an HTML report based on their test execution results. If a user hasn't SET `TESTOMATIO` environment, the report will still be generated**
-
-```
-TESTOMATIO_HTML_REPORT_SAVE=1 <actual run command>
-```
-
-### Enabling HTML Reports
-
-To enable HTML reports, set the TESTOMATIO_HTML_REPORT_SAVE environment variable to 1. Additionally, you can customize the HTML report folder and filename using the following variables:
-
-- TESTOMATIO_HTML_REPORT_SAVE=1
-- TESTOMATIO_HTML_REPORT_FOLDER: Specify the folder for HTML reports
-- TESTOMATIO_HTML_FILENAME: Set the desired filename for the HTML report
-
-_!!!Please note that the name must include the extension ".html". If the extension is missing, the report will be saved with the default name = testomatio-report.html_
-
-### Usage
-
-The HTML Pipe operates as part of the test execution process. When running your tests with the specified environment variables, the HTML Pipe will generate reports based on the test results.
-
-### Report Generation
-
-Once the test run is complete, the HTML Pipe compiles the test results and generates an HTML report. The generated report is saved to the specified HTML output path.
-
-The HTML report includes essential information, such as run ID, status, parallel execution indication, run URL, execution time, execution date, and details of individual tests.
-
-#### Example Command
-
-📊 Generate a report without triggering the TESTOMATIO pipe (no data sent to the client)
-
-_Execute the following command to generate a report without sending data to TESTOMATIO:_
-
-```
-TESTOMATIO_HTML_REPORT_SAVE=1 npx codeceptjs run
-
-```
-
-📝 Generate a report based on the default folder/html-file name: This command triggers the test execution process and enables the HTML Pipe to generate reports based on the test results:
-
-- Output folder: html-report/
-- Output file: testomatio-report.html
-
-_Execute the following command to generate a report with default settings:_
-
-```
-TESTOMATIO_HTML_REPORT_SAVE=1 TESTOMATIO={API_KEY} npx codeceptjs run
-
-```
-
-📂 Generate a report based on a custom HTML folder/html-file name.
-**!!!You can SET only one of the following parameters if needed: folder or file name**
-
-_Execute the following command to generate a report with both folder & file names:_
-
-```
-TESTOMATIO_HTML_REPORT_SAVE=1 TESTOMATIO_HTML_REPORT_FOLDER=user-html-reporter TESTOMATIO_HTML_FILENAME=custom.html TESTOMATIO={API_KEY} npx codeceptjs run
-
-```
-
-🖥️ An example of a report can be seen in the screenshot below:
-
-![HTML example](./images/html-pipe.png)
-

package/skills/testeiya/testomatio-docs/docs/test-reporting/pipes/index.mdx

@@ -1,57 +0,0 @@
----
-title: Pipes
-description: Testomat.io's Pipes feature allows you to forward test data from your test framework to other services like GitHub, GitLab, or CSV reports. Pipes are configured via environment variables and can be customized to send data to analytics, databases, or notifications. You can also create custom pipes for specific needs, ensuring compatibility across different test frameworks.
-type: article
-url: https://docs.testomat.io/test-reporting/pipes/overview
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, Pipes, test reporting, GitHub integration, GitLab, CSV reports, CI pipelines, custom pipes, environment variables, test frameworks
----
-
-import DirectoryLinks from '/src/components/DirectoryLinks.astro';
-
-<DirectoryLinks directory="test-reporting/pipes" />
-
-## 📯 Pipes
-
-### What are Pipes?
-
-Unlike other reporters, Testomat.io Reporter doesn't force you to report data only to Testomat.io application. Testomat.io Reporter collects data from test frameworks and submits it via pipes to other services.
-
-![](./images/reporter-pipes.png)
-
-For instance, you can enable GitHub Pipe to create a comment on a GitHub Pull Request and CSV Export Pipe to write a report in CSV format. To report data to Testomat.io App, Testomat.io Pipe should be enabled, but not required if you don't plan to use Testomat.io App. You can also write your own pipe to:
-
-- 📈 send data to analytics storage
-- 🗄 store data into database
-- 📧 send emails
-- 💬 send notifications to chats
-- etc....
-
-Pipes work in the very same manner for all supported test frameworks, as well as for JUnit reports. So writing a pipe instead of a custom reporter for a particular framework, saves your time as you can be sure, this pipe will work with any attached test result.
-
-Testomat.io Reporter doesn't store test data in any internal format. Test data is processed in memory. While a test is running, all pipes are notified of changes.
-
-Pipes Concepts:
-
-- **Pipes are configured via environment variables** - each test framework has its own configuration (or not). To ensure that a pipe receives its configuration it is independent from a running test framework.
-- **Pipes are enabled if a corresponding environment variables are set** - for instance, if `TESTOMATIO` variable is present, Testomat.io Pipe is enabled, if `GH_PAT` variable is set, GitHub Pipe is enabled.
-- **Custom Pipes** can be created as modules and added to `package.json` file.
-- When used locally environment variables are expected to be set in `.env` file. When running on CI server use Environment Configuration a CI server provides to pass environment variables into the pipeline.
-
-### Built-in Pipes
-
-- [Testomat.io](https://docs.testomat.io/test-reporting/pipes/testomatio)
-- [GitHub](https://docs.testomat.io/test-reporting/pipes/github)
-- [Gitlab](https://docs.testomat.io/test-reporting/pipes/gitlab)
-- [CSV](https://docs.testomat.io/test-reporting/pipes/csv)
-- [Bitbucket](https://docs.testomat.io/test-reporting/pipes/bitbucket)
-- [Debugging](https://docs.testomat.io/test-reporting/pipes/debug)
-
-## Custom Pipe
-
-_to be updated_
-
-....

package/skills/testeiya/testomatio-docs/docs/test-reporting/pipes/testomatio.md

@@ -1,331 +0,0 @@
----
-title: Advanced Options
-description: Learn how to use the Testomat.io Pipe for advanced reporting configurations in test automation. The guide covers setting environment variables, adding reports to test runs, managing parallel executions, filtering tests, and integrating with JIRA for issue tracking.
-type: article
-url: https://docs.testomat.io/test-reporting/pipes/testomatio
-head:  
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Test reporting, test automation, Testomat.io Pipe, environment variables, CI integration, parallel execution, test filtering, JIRA integration, build URL, test management
----
-## Testomat.io Pipe
-
-![](./images/testomatio.png)
-
-Testomat.io Pipe sends data to [Testomat.io Application](https://app.testomat.io). Testomat.io provides free projects forever and unlimited test runs. Even it is a cloud application you can use it for free.
-
-**🔌 To enable Testomat.io pipe set `TESTOMATIO` environment variable with API key provided by Testomatio.**
-
-```
-TESTOMATIO={API_KEY} <actual run command>
-```
-
-Here are some possible use cases where you can use additional configuration on reporter:
-
-- [Create Unmatched Tests](#create-unmatched-tests)
-- [Add Report to Run by ID](#add-report-to-run-by-id)
-- [Do Not Finalize Run](#do-not-finalize-run)
-- [Setting Report Title](#setting-report-title)
-- [Reporting Parallel Execution to To Same Run](#reporting-parallel-execution-to-to-same-run)
-- [Adding Report to RunGroup](#adding-report-to-rungroup)
-- [Adding Environments to Run](#adding-environments-to-run)
-- [Starting an Empty Run](#starting-an-empty-run)
-- [Manually Finishing Run](#manually-finishing-run)
-- [Setting Build URL](#setting-build-url)
-- [Publish Run](#publish-run)
-- [Assign Label To Run](#assign-label-to-run)
-- [Create Jira Issue for Run](#create-jira-issue-for-run)
-- [Filter Tests](#filter-tests)
-
-### Create Unmatched Tests
-
-Testomat.io will not create tests from the report if they have not been previously imported. To create tests during the report `TESTOMATIO_CREATE` option can be used:
-
-```bash
-TESTOMATIO={API_KEY} TESTOMATIO_CREATE=1 <actual run command>
-```
-
-### Add Report to Run by ID
-
-This feature is widely used when a run is executed on CI.
-A run is created before the test is started and it is marked as `scheduled`. Then
-a report is assigned to that run using `TESTOMATIO_RUN` environment variable and `{RUN_ID}` of a run:
-
-```bash
-TESTOMATIO={API_KEY} TESTOMATIO_RUN={RUN_ID} <actual run command>
-```
-
-### Do Not Finalize Run
-
-If multiple reports are added to the same run, each of them should not finalize the run.
-In this case use `TESTOMATIO_PROCEED=1` environment variable, so the Run will be shown as `Running`
-
-```
-TESTOMATIO={API_KEY} TESTOMATIO_PROCEED=1 TESTOMATIO_RUN={RUN_ID} <actual run command>
-```
-
-After all reports were attached and run can be execute the following command:
-
-```
-TESTOMATIO={API_KEY} TESTOMATIO_RUN={RUN_ID} npx @testomatio/reporter finish
-```
-
-### Setting Report Title
-
-Give a title to your reports by passing it as environment variable to `TESTOMATIO_TITLE`.
-
-```bash
-TESTOMATIO={API_KEY} TESTOMATIO_TITLE="title for the report" <actual run command>
-```
-
-### Reporting Parallel Execution to To Same Run
-
-Provide a shared unique title to all runs that will be running in parallel, and add `TESTOMATIO_SHARED_RUN` environment var. So all reports will be sent to this run.
-
-```bash
-TESTOMATIO={API_KEY} TESTOMATIO_TITLE="report for commit ${GIT_COMMIT}" TESTOMATIO_SHARED_RUN=1 <actual run command>
-```
-
-We recommend using a commit hash as a title to create a new Run. In this case we ensure that run title is unique and will be the same for all parallel jobs running exactly for this commit.
-
-By default you can report to the same run if a run was created no more than 20 minutes ago. If you want to increase this time you can use `TESTOMATIO_SHARED_RUN_TIMEOUT` environment variable. `TESTOMATIO_SHARED_RUN_TIMEOUT`accepts value in minutes, so to increase timeout to 2 hours (120 minutes) use the following command:
-
-```bash
-TESTOMATIO={API_KEY} TESTOMATIO_TITLE="report for commit ${GIT_COMMIT}" TESTOMATIO_SHARED_RUN=1 TESTOMATIO_SHARED_RUN_TIMEOUT=120 <actual run command>
-```
-
-### Adding Report to RunGroup
-
-Create/Add run to group by providing `TESTOMATIO_RUNGROUP_TITLE`:
-
-```sh
-TESTOMATIO={API_KEY} TESTOMATIO_RUNGROUP_TITLE="Build ${BUILD_ID}" <actual run command>
-```
-
-### Adding Environments to Run
-
-Add environments to run by providing `TESTOMATIO_ENV` as comma seperated values:
-
-```bash
-TESTOMATIO={API_KEY} TESTOMATIO_ENV="Windows, Chrome" <actual run command>
-```
-
-### Starting an Empty Run
-
-If you want to create a run and obtain its `{RUN_ID}` from [testomat.io](https://testomat.io) you can use `--launch` option:
-
-```bash
-TESTOMATIO={API_KEY} npx @testomatio/reporter start
-```
-
-This command will return `{RUN_ID}` which you can pass to other jobs in a workflow.
-
-> When executed with `--launch` a command provided by `-c` flag is ignored
-
-### Manually Finishing Run
-
-If you want to finish a run started by `--launch` use `--finish` option. `TESTOMATIO_RUN` environment variable is required:
-
-```bash
-TESTOMATIO={API_KEY} TESTOMATIO_RUN={RUN_ID} npx @testomatio/reporter finish
-```
-
-### Setting Build URL
-
-When running on CI reporter tries to detect automatically the URL of the current build. This URL will be set to Run report. Reporter automatically detects build URL for following CI services:
-
-- GitHub Actions
-- Azure Devops
-- Jenkins
-- CircleCi
-- Gitlab CI
-
-If you are using a different CI or you want to override build url run tests with `BUILD_URL` environment variable:
-
-```bash
-TESTOMATIO={API_KEY} BUILD_URL=<build-url> <actual run command>
-```
-
-### Publish Run
-
-To make report publicly available pass `TESTOMATIO_PUBLISH=1` variable:
-
-```
-TESTOMATIO={API_KEY} TESTOMATIO_PUBLISH=1 <actual run command>
-```
-
-### Assign Label To Run
-
-To assign a label to run, a **label with scope `runs` must exist**.
-Then a label can be passed via `TESTOMATIO_LABEL` variable:
-
-```
-TESTOMATIO={API_KEY} TESTOMATIO_LABEL=release <actual run command>
-```
-
-There is a way to pass a value to label via `:`:
-
-```
-TESTOMATIO={API_KEY} TESTOMATIO_LABEL="module:checkout" <actual run command>
-```
-
-Or you can set multiple labels separating them with comma:
-
-```
-TESTOMATIO={API_KEY} TESTOMATIO_LABEL="release,module:checkout" <actual run command>
-```
-
-### Create Jira Issue for Run
-
-To automatically assign Run to Jira Issue pass the ID of that issue as `TESTOMATIO_JIRA_ID` variable
-
-```
-TESTOMATIO={API_KEY} TESTOMATIO_JIRA_ID={Jira_Issue_ID} <actual run command>
-```
-
-For example, if your Jira issue id is `TST-1`, command should be:
-
-```
-TESTOMATIO={API_KEY} TESTOMATIO_JIRA_ID=TST-1 <actual run command>
-```
-
-### Filter Tests
-
-Testomatio allows you to enhance your test execution with the option to filter and manage test runs based on various criteria. This can help you efficiently organize and execute your tests. Below, we explain how to use the `--filter` option in conjunction with Testomatio for customized test runs.
-
-> The filtering functionality for test execution is currently available for the following frameworks: Playwright & CodeceptJS.
-
-To use the `--filter` option with Testomatio, follow the format:
-
-```bash
-TESTOMATIO={API_KEY} npx @testomatio/reporter run <actual run command> --filter 'testomatio:{filter-type}={filter-value}'
-```
-
-#### Available Filter Types
-
-**Tag Name Filter**
-
-Filter tests by tag names. Use this filter to select tests associated with specific tags.
-
-![Tag Name Filter](./images/by-tag-name.png)
-
-_Command execution example_
-
-```bash
-TESTOMATIO={API_KEY} npx @testomatio/reporter run 'actual run command' --filter 'testomatio:tag-name=smoke'
-```
-
-**Plan ID Filter**
-
-Filter tests by Testomatio plan IDs. Use this filter to organize and execute tests based on plan IDs.
-
-![Plan ID Filter](./images/by-plan-id.png)
-
-_Command execution example_
-
-```bash
-TESTOMATIO={API_KEY} npx @testomatio/reporter run 'actual run command' --filter 'testomatio:plan-id=b62f3170'
-```
-
-**Label Filter**
-
-Filter tests using custom labels. Labels allow you to categorize tests for better management and execution.
-
-Label Filter (by label name) Example 1:
-![Label Filter Example 3](./images/by-label-1.png)
-
-Label Filter (by label id) Example 2:
-![Label Filter Example 1](./images/by-label.png)
-
-Another Label Filter Example 3:
-![Label Filter Example 2](./images/by-label-3.png)
-
-_Command execution example_
-
-```bash
-TESTOMATIO={API_KEY} npx @testomatio/reporter run 'actual run command' --filter 'testomatio:label=new-label-test'
-```
-
-OR
-
-```bash
-TESTOMATIO={API_KEY} npx @testomatio/reporter run 'actual run command' --filter 'testomatio:label=NEW label TEST'
-```
-
-**Label Filter based on the Severity type**
-
-If you want to use a specific severity type, you should join the "severity" label id + severity type(e.g.: `s1-id2:⛔ Blocker`).
-
-Here's a list of available types that you can copy and add to the run command:
-
-- ⚠️ Critical
-- ⛔ Blocker
-- 🔥 Major
-- 👌 Normal
-- ❄️ Minor
-- 💤 Trivial
-
-Label Filter Example based on the Severity type:
-![Label Filter Example 3](./images/by-label-severity.png)
-
-_Command execution example_
-
-```bash
-TESTOMATIO={API_KEY} npx @testomatio/reporter run 'actual run command' --filter 'testomatio:label=severity-f1b11:🔥 Major'
-```
-
-OR
-
-```bash
-TESTOMATIO={API_KEY} npx @testomatio/reporter run 'actual run command' --filter 'testomatio:label=NEW label TEST:💤 Trivial'
-```
-
-**JIRA Ticket Filter**
-
-Filter tests linked to JIRA tickets. Use this filter to coordinate testing efforts with your JIRA workflow.
-
-![JIRA Ticket Filter](./images/by-jira-id.png)
-
-_Command execution example_
-
-```bash
-TESTOMATIO={API_KEY} npx @testomatio/reporter run 'actual run command' --filter 'testomatio:jira-ticket=LMP-51'
-```
-
-**📚 Example Usage**
-
-For instance, if you want to run tests with a specific label named "new-label-test," you can use the following command:
-
-```bash
-TESTOMATIO={API_KEY} npx @testomatio/reporter run 'npx codeceptjs run' --filter 'testomatio:label=new-label'
-```
-
-OR using Playwright:
-
-```bash
-TESTOMATIO={API_KEY} npx @testomatio/reporter run 'npx playwright test' --filter 'testomatio:label=new-label'
-```
-
-> Remember to replace {API_KEY} with your actual Testomatio API key and adjust the `<actual run command>` according to your testing setup
-
-> It's important to note that the provided filter value must match exactly the corresponding tag name, plan ID, label, or JIRA ticket for the desired tests
-
-Please note, that this functionality allows you to easily filter and execute tests based on specific criteria, enhancing your testing experience.
-
-### Exclude Tests from Report by Glob Pattern
-
-To exclude tests from the report by [glob pattern](https://www.npmjs.com/package/glob) use `TESTOMATIO_EXCLUDE_FILES_FROM_REPORT_GLOB_PATTERN` environment variable:
-
-```bash
-TESTOMATIO={API_KEY} TESTOMATIO_EXCLUDE_FILES_FROM_REPORT_GLOB_PATTERN="**/*.setup.ts" <actual run command>
-```
-
-You can use multiple patterns separated by `;`:
-
-```bash
-TESTOMATIO={API_KEY} TESTOMATIO_EXCLUDE_FILES_FROM_REPORT_GLOB_PATTERN="**/*.setup.ts;tests/*.auth.js" <actual run command>
-```
-
-(Any files in `node_modules` will be ignored).
-

package/skills/testeiya/testomatio-docs/docs/test-reporting/python.md

@@ -1,229 +0,0 @@
----
-title: Python Test Frameworks
-description: Learn how to integrate the Testomat.io reporter with Python test frameworks like Pytest. The documentation covers installation, synchronizing tests, configuring test environments, reporting results, and submitting test artifacts. It also includes detailed configuration options such as managing test artifacts through S3 and setting up environment variables for reporting.
-type: article
-url: https://docs.testomat.io/test-reporting/python
-head:  
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Python test frameworks, Pytest, Testomat.io, test synchronization, test reporting, test artifacts, automation, S3 storage, test configuration, API integration, continuous integration, environment setup
----
-
-:::note
- Taken from [Pytestomatio Reporter Readme](https://github.com/testomatio/pytestomatio)
-:::
-
-[![Support Ukraine Badge](https://bit.ly/support-ukraine-now)](https://github.com/support-ukraine/support-ukraine)
-
-# testomat.io plugin for pytest
-
-## uses testomat.io API:
-
-- https://testomatio.github.io/check-tests/
-- https://testomatio.github.io/reporter/
-
-## Installation
-
-```bash
-pip install pytestomatio
-```
-
-## Usage
-
-Synchronize tests to testomat.io and get back test id.
-Tests will not be executed
-
-```bash
-pytest --testomatio sync
-```
-
-Remove all test ids from source code. Tests will not be executed
-
-```bash
-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
-
-```bash
-pytest --testomatio report
-```
-
-Run pytest with debug parameter to get test data collected in metadata.json file
-
-```bash
-pytest --testomatio debug
-```
-
-## Configuration with environment variables
-You can use environment variable to control certain features of testomat.io
-
-| Env variable |  What it does | Examples |
-|--------|--------|-------|
-| TESTOMATIO| Provides token for pytestomatio to access and push data to testomat.io | TESTOMATIO=tstmt_***** pytest --testomatio sync|
-|TESTOMATIO_RUN|Name of a test run to create on testomat.io|TESTOMATIO_RUN="Smoke test" pytest --testomatio report|
-|TESTOMATIO_RUN_ID| Id of existing test run to use for sending test results to | TESTOMATIO_RUN_ID=98dfas0 pytest --testomatio report |
-|TESTOMATIO_RUNGROUP_TITLE| Create a group (folder) for a test run | TESTOMATIO_RUNGROUP_TITLE="Release 2.0" pytest --testomatio report|
-|TESTOMATIO_ENV|Assign environment to a test run |TESTOMATIO_ENV="linux,chrome,1920x1080" pytest --testomatio report|
-|TESTOMATIO_LABELS|Assign labels to a test run |TESTOMATIO_ENV="smoke,regression" pytest --testomatio report|
-|TESTOMATIO_SYNC_LABELS|Assign labels to a test case when you synchronise test from code with testomat.io|TESTOMATIO_SYNC_LABELS="number:1,list:one,standalone" pytest --testomatio report|
-|TESTOMATIO_CODE_STYLE|If you are not sure, don't set this variable. Default value is 'default'|TESTOMATIO_CODE_STYLE=pep8 pytest --testomatio sync|
-|TESTOMATIO_CI_DOWNSTREAM|If set, pytestomatio will not set or update build url for a test run. This is useful in scenarios where build url is already set in the test run by Testomat.io for test runs that a created directly on Testomat.io.|TESTOMATIO_CI_DOWNSTREAM=true pytest --testomatio report|
-
-
-### 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
-
-```ini
-[pytest]
-testomatio_url = https://app.testomat.io
-
-```
-
-### Submitting Test Run Environment
-
-to configure test environment, you can use additional option:
-
-```bash
-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, BUCKET_PATH`
-
-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](https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures)
-
-```python
-# content of conftest.py
-import pytest
-import random
-import os
-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.
-
-2) If you prefer to use pytest hooks - add `pytest_runtest_makereport` hook in your `conftest.py` file.
-
-```python
-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.
-
-```python
-from pytest import mark
-
-
-@mark.testomatio('@T96c700e6')
-def test_example():
-    assert 2 + 2 == 4
-```
-
-### Compatibility table with [Testomatio check-tests](https://github.com/testomatio/check-tests)
-
-| Action |  Compatibility | Method |
-|--------|--------|-------|
-| Report tests to testomat.io | complete | `pytest --testomatio report` |
-| Filter test by id to run | complete | `pytest --testomatio report --test-id="T00C73028\|T00C73029"` |
-| 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-detach` |
-| 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 sync --directory "Windows\smoke"` |
-| Debugging | parity | `pytest --testomatio debug` |
-
-
-## Test
-- import into empty project
-- updated test - (resync)
-- test run
-- test run into a folder
-- test run labels, tags
-
-## TODO
-- retry test run update with less attributes, we get 500 from api
-- handler non configured s3 bucket error
-- Fix test duration
-
-## Contribution
-Use python 3.12
-
-1. `pip install ".[dev]"`
-1. `python ./smoke.py`
-1. Test things manually
-1. Verify no regression bugs
-1. `cz commit`
-1. `cz bump`
-1. `git push remoteName branchName --tags`