semvec/pypi-packages huggingface dataset:
cmk-werk-zeug 0.1.5
cmk-werk-zeug
Requires Python: <4,>=3.12

# CWZ - CMK-Werk-Zeug

This is both a collection of tools and shared libraries created for (but not limited to) Checkmk development
and a 'collector' for other tools located in different repositories.


## What you get

For now you only get `cmk-components` - a tool for listing component/code ownership details of the
`check_mk` repository via Gerrit and the `code-owners` plugin


## Install

You either clone the cwz repository (`ssh://review.lan.tribe29.com:29418/cmk-werk-zeug`) and make it's tools available
via `uv` or you install the pip package:

```
pipx install cmk-werk-zeug
```

For ci_build_metrics you need PostgreSQL installed
```
sudo apt install postgresql postgresql-contrib postgresql-server-dev
```
qase-tavern 3.0.0
Qase Tavern Plugin for Qase TestOps and Qase Report
Requires Python: >=3.9
Keywords: qase, tavern, plugin, testops, report, qase reporting, test observability

# [Qase TestOps](https://qase.io) Tavern Reporter

[![License](https://lxgaming.github.io/badges/License-Apache%202.0-blue.svg)](https://www.apache.org/licenses/LICENSE-2.0)

## Installation

To install the latest version, run:

```sh
pip install pre qase-tavern
```

## Getting started

The Tavern reporter can auto-generate test cases
and suites from your test data.
Test results of subsequent test runs will match the same test cases
as long as their names and file paths don't change.

You can also annotate the tests with the IDs of existing test cases
from Qase.io before executing tests. It's a more reliable way to bind
autotests to test cases, that persists when you rename, move, or
parameterize your tests.

For detailed instructions on using annotations and methods, refer to [Usage](docs/usage.md).

### Multi-Project Support

Qase Tavern Reporter supports sending test results to multiple Qase projects simultaneously. 
You can specify different test case IDs for each project using the `QaseProjectID.PROJECT_CODE=IDS` format in test names.

For detailed information and examples, see the [Multi-Project Support](docs/usage.md#multi-project-support) section in the usage documentation.

For example:

```yaml
---
test_name: QaseID=1 Test with QaseID success

stages:
  - name: Step 1
    request:
    response:

  - name: Step 2
    request:
    response:
```

To execute Tavern tests and report them to Qase.io, run the command:

```bash
pytest
```

You can try it with the example project at [`examples/tavern`](../examples/tavern/).

## Configuration

Qase Tavern Reporter is configured in multiple ways:

- using a config file `qase.config.json`
- using environment variables
- using command line options

Environment variables override the values given in the config file,
and command line options override both other values.

Configuration options are described in the
[configuration reference](docs/CONFIGURATION.md).

### Example: qase.config.json

```json
{
  "mode": "testops",
  "fallback": "report",
  "testops": {
    "project": "YOUR_PROJECT_CODE",
    "api": {
      "token": "YOUR_API_TOKEN",
      "host": "qase.io"
    },
    "run": {
      "title": "Test run title"
    },
    "batch": {
      "size": 100
    }
  },
  "report": {
    "driver": "local",
    "connection": {
      "local": {
        "path": "./build/qase-report",
        "format": "json"
      }
    }
  },
  "logging": {
    "console": true,
    "file": false
  },
  "environment": "local"
}
```

## Requirements

We maintain the reporter on [LTS versions of Python](https://devguide.python.org/versions/).

`python >= 3.9`
`tavern >= 2.11.0`

<!-- references -->

[auth]: https://developers.qase.io/#authentication