[](https://opensource.org/licenses/EPL-2.0)
[]()
[]()
[](https://ci.eclipse.org/kiso-testing/job/kiso-testing/job/master/)
[](https://kiso-testing.readthedocs.io/en/latest/?badge=latest)
[](https://ci.eclipse.org/kiso-testing/job/kiso-testing/job/master/)
[](https://codecov.io/gh/eclipse/kiso-testing)
[](https://www.codefactor.io/repository/github/eclipse/kiso-testing)
[]()
[]()
# PyKiso
## Introduction ##
**pykiso** is an integration test framework. With it, it is possible to write
* Whitebox integration tests directly on my target device
* Graybox integration tests to make sure the communication-link with my target device is working as expected
* Blackbox integration tests to make sure my external device interfaces are working as expected
The project will contain:
* The core python framework (this repository)
* Framework plugins that are generic enough to be integrated as "native" (this repository)
* Additional "testApps" for different targets platforms (e.g. stm32, ...) or languages (C, C++, ...) . It could be pure SW or also HW (other repositories)
## Link to Eclipse Project
https://projects.eclipse.org/projects/iot.kiso-testing
## Requirements ##
* Python 3.7+
* pip/poetry (used to get the rest of the requirements)
## Install ##
```bash
pip install pykiso # Core framework
pip install pykiso[plugins] # For installing all plugins
pip install pykiso[all] # For installing all what we have to offer
```
[Poetry](https://python-poetry.org/) is more appropriate for developers as it automatically creates virtual environments.
```bash
cd kiso-testing
poetry install --all-extras
poetry shell
```
### Pre-Commit
To improve code-quality, a configuration of [pre-commit](https://pre-commit.com/) hooks are available.
The following pre-commit hooks are used:
- ruff-format
- flake8
- isort
- trailing-whitespace
- end-of-file-fixer
- check-docstring-first
- check-json
- check-added-large-files
- check-yaml
- debug-statements
If you don't have pre-commit installed, you can get it using pip:
```bash
pip install pre-commit
```
Start using the hooks with
```bash
pre-commit install
```
## Commit message convention
Commits are sorted into multiple categories based on keywords that can occur at any position as part of the commit message.
[Category] Keywords
* [BREAKING CHANGES] BREAKING CHANGE
* [Features] feat:
* [Fixes] fix:
* [Docs] docs:
* [Styles] style:
* [Refactors] refactor!:
* [Performances] perf:
* [Tests] test:
* [Build] build:
* [Ci] ci:
Each commit is considered only once according to the order of the categories listed above. Merge commits are ignored.
The tool commitizen can help you to create commits which follows these standards.
```bash
# if not yet installed:
pip install -U commitizen==2.20.4
# helps you to create a commit:
cz commit
# or use equivalent short variant:
cz c
```
## Generate Changelog
After you installed the dev dependencies from the pipfile you are able to
autogenerate the Changelog.
```bash
invoke changelog
```
## Usage ##
Once installed the application is bound to `pykiso`, it can be called with the following arguments:
```bash
Usage: pykiso [OPTIONS]
Embedded Integration Test Framework - CLI Entry Point.
TAG Filters: any additional option to be passed to the test as tag through
the pykiso call. Multiple values must be separated with a comma.
For example: pykiso -c your_config.yaml --branch-level dev,master --variant
delta
Options:
-c, --test-configuration-file FILE
path to the test configuration file (in YAML
format) [required]
-l, --log-path PATH path to log-file or folder. If not set will
log to STDOUT
--log-level [DEBUG|INFO|WARNING|ERROR]
set the verbosity of the logging
--junit enables the generation of a junit report
--text default, test results are only displayed in
the console
--step-report PATH generate the step report at the specified
path
--failfast stop the test run on the first error or
failure
-v, --verbose activate the internal framework logs
-p, --pattern TEXT test filter pattern, e.g. 'test_suite_1.py'
or 'test_*.py'. Or even more granularly
'test_suite_1.py::test_class::test_name'
--version Show the version and exit.
-h, --help Show this message and exit.
--logger Change the logger class used in pykiso, value
is the import path to the logger class, example
'logging.Logger'
```
Suitable config files are available in the `examples` folder.
### Demo using example config ##
```bash
invoke run
```
### Running the Tests ##
```bash
invoke test
```
or
```bash
pytest
```
Raw data
{
"_id": null,
"home_page": "https://pypi.org/project/pykiso/",
"name": "pykiso",
"maintainer": null,
"docs_url": null,
"requires_python": "<4.0,>=3.7",
"maintainer_email": null,
"keywords": "testing, integration testing, framework, testing framework",
"author": "Sebastian Fischer",
"author_email": "sebastian.fischer@de.bosch.com",
"download_url": "https://files.pythonhosted.org/packages/fe/61/689316f5a0c390b78da74fac50b35d723014c725cb1535482f178ad3e6da/pykiso-0.28.0.tar.gz",
"platform": null,
"description": "[](https://opensource.org/licenses/EPL-2.0)\n[]()\n[]()\n[](https://ci.eclipse.org/kiso-testing/job/kiso-testing/job/master/)\n[](https://kiso-testing.readthedocs.io/en/latest/?badge=latest)\n[](https://ci.eclipse.org/kiso-testing/job/kiso-testing/job/master/)\n[](https://codecov.io/gh/eclipse/kiso-testing)\n[](https://www.codefactor.io/repository/github/eclipse/kiso-testing)\n[]()\n[]()\n\n# PyKiso\n\n\n\n## Introduction ##\n\n**pykiso** is an integration test framework. With it, it is possible to write\n* Whitebox integration tests directly on my target device\n* Graybox integration tests to make sure the communication-link with my target device is working as expected\n* Blackbox integration tests to make sure my external device interfaces are working as expected\n\nThe project will contain:\n* The core python framework (this repository)\n* Framework plugins that are generic enough to be integrated as \"native\" (this repository)\n* Additional \"testApps\" for different targets platforms (e.g. stm32, ...) or languages (C, C++, ...) . It could be pure SW or also HW (other repositories)\n\n## Link to Eclipse Project\nhttps://projects.eclipse.org/projects/iot.kiso-testing\n\n## Requirements ##\n\n* Python 3.7+\n* pip/poetry (used to get the rest of the requirements)\n\n## Install ##\n\n```bash\npip install pykiso # Core framework\npip install pykiso[plugins] # For installing all plugins\npip install pykiso[all] # For installing all what we have to offer\n```\n\n[Poetry](https://python-poetry.org/) is more appropriate for developers as it automatically creates virtual environments.\n\n```bash\ncd kiso-testing\npoetry install --all-extras\npoetry shell\n```\n\n### Pre-Commit\n\nTo improve code-quality, a configuration of [pre-commit](https://pre-commit.com/) hooks are available.\nThe following pre-commit hooks are used:\n\n- ruff-format\n- flake8\n- isort\n- trailing-whitespace\n- end-of-file-fixer\n- check-docstring-first\n- check-json\n- check-added-large-files\n- check-yaml\n- debug-statements\n\nIf you don't have pre-commit installed, you can get it using pip:\n\n```bash\npip install pre-commit\n```\n\nStart using the hooks with\n\n```bash\npre-commit install\n```\n\n## Commit message convention\n\nCommits are sorted into multiple categories based on keywords that can occur at any position as part of the commit message.\n[Category] Keywords\n* [BREAKING CHANGES] BREAKING CHANGE\n* [Features] feat:\n* [Fixes] fix:\n* [Docs] docs:\n* [Styles] style:\n* [Refactors] refactor!:\n* [Performances] perf:\n* [Tests] test:\n* [Build] build:\n* [Ci] ci:\nEach commit is considered only once according to the order of the categories listed above. Merge commits are ignored.\n\nThe tool commitizen can help you to create commits which follows these standards.\n```bash\n# if not yet installed:\npip install -U commitizen==2.20.4\n# helps you to create a commit:\ncz commit\n# or use equivalent short variant:\ncz c\n```\n\n## Generate Changelog\n\nAfter you installed the dev dependencies from the pipfile you are able to\nautogenerate the Changelog.\n\n```bash\ninvoke changelog\n```\n\n## Usage ##\n\nOnce installed the application is bound to `pykiso`, it can be called with the following arguments:\n\n```bash\nUsage: pykiso [OPTIONS]\n\n Embedded Integration Test Framework - CLI Entry Point.\n\n TAG Filters: any additional option to be passed to the test as tag through\n the pykiso call. Multiple values must be separated with a comma.\n\n For example: pykiso -c your_config.yaml --branch-level dev,master --variant\n delta\n\nOptions:\n -c, --test-configuration-file FILE\n path to the test configuration file (in YAML\n format) [required]\n -l, --log-path PATH path to log-file or folder. If not set will\n log to STDOUT\n --log-level [DEBUG|INFO|WARNING|ERROR]\n set the verbosity of the logging\n --junit enables the generation of a junit report\n --text default, test results are only displayed in\n the console\n --step-report PATH generate the step report at the specified\n path\n --failfast stop the test run on the first error or\n failure\n -v, --verbose activate the internal framework logs\n -p, --pattern TEXT test filter pattern, e.g. 'test_suite_1.py'\n or 'test_*.py'. Or even more granularly\n 'test_suite_1.py::test_class::test_name'\n --version Show the version and exit.\n -h, --help Show this message and exit.\n --logger Change the logger class used in pykiso, value\n is the import path to the logger class, example\n 'logging.Logger'\n```\n\nSuitable config files are available in the `examples` folder.\n\n### Demo using example config ##\n\n```bash\ninvoke run\n```\n\n### Running the Tests ##\n\n```bash\ninvoke test\n```\n\nor\n\n```bash\npytest\n```\n",
"bugtrack_url": null,
"license": "Eclipse Public License - v 2.0",
"summary": "Embedded integration testing framework.",
"version": "0.28.0",
"project_urls": {
"Documentation": "https://kiso-testing.readthedocs.io/en/latest/",
"Homepage": "https://pypi.org/project/pykiso/",
"Repository": "https://github.com/eclipse/kiso-testing"
},
"split_keywords": [
"testing",
" integration testing",
" framework",
" testing framework"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "75234afba484ce33dc68e9396f9b0b434090e3adba8020f3de99649a48a9b07a",
"md5": "60aa571e2818d14ab122e14439469b6f",
"sha256": "6a3e70bcb65cc66b2f9a55099a893b9e788b28bb12d41af77743943c30fbbcc1"
},
"downloads": -1,
"filename": "pykiso-0.28.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "60aa571e2818d14ab122e14439469b6f",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": "<4.0,>=3.7",
"size": 247602,
"upload_time": "2024-03-28T16:20:43",
"upload_time_iso_8601": "2024-03-28T16:20:43.214144Z",
"url": "https://files.pythonhosted.org/packages/75/23/4afba484ce33dc68e9396f9b0b434090e3adba8020f3de99649a48a9b07a/pykiso-0.28.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "fe61689316f5a0c390b78da74fac50b35d723014c725cb1535482f178ad3e6da",
"md5": "70edc6c3275a054ba6fc61588445ebd9",
"sha256": "e6dcf476a2e9a03c1fcdf6bf0bc87ca7f33ddd4a886006bafe5458747406fcbf"
},
"downloads": -1,
"filename": "pykiso-0.28.0.tar.gz",
"has_sig": false,
"md5_digest": "70edc6c3275a054ba6fc61588445ebd9",
"packagetype": "sdist",
"python_version": "source",
"requires_python": "<4.0,>=3.7",
"size": 177492,
"upload_time": "2024-03-28T16:20:44",
"upload_time_iso_8601": "2024-03-28T16:20:44.909187Z",
"url": "https://files.pythonhosted.org/packages/fe/61/689316f5a0c390b78da74fac50b35d723014c725cb1535482f178ad3e6da/pykiso-0.28.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-03-28 16:20:44",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "eclipse",
"github_project": "kiso-testing",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"tox": true,
"lcname": "pykiso"
}
JSON
