tquality-py-core 0.1.4__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- tquality_py_core-0.1.4/.gitignore +16 -0
- tquality_py_core-0.1.4/CONTRIBUTING.md +196 -0
- tquality_py_core-0.1.4/LICENSE +201 -0
- tquality_py_core-0.1.4/NOTICE +5 -0
- tquality_py_core-0.1.4/PKG-INFO +185 -0
- tquality_py_core-0.1.4/README.md +154 -0
- tquality_py_core-0.1.4/pyproject.toml +106 -0
- tquality_py_core-0.1.4/schema/config.schema.json +36 -0
- tquality_py_core-0.1.4/scripts/install-hooks.sh +47 -0
- tquality_py_core-0.1.4/src/tquality_core/__init__.py +27 -0
- tquality_py_core-0.1.4/src/tquality_core/cli.py +107 -0
- tquality_py_core-0.1.4/src/tquality_core/config.py +158 -0
- tquality_py_core-0.1.4/src/tquality_core/elements/__init__.py +4 -0
- tquality_py_core-0.1.4/src/tquality_core/elements/base_element.py +82 -0
- tquality_py_core-0.1.4/src/tquality_core/elements/locator.py +26 -0
- tquality_py_core-0.1.4/src/tquality_core/pages/__init__.py +3 -0
- tquality_py_core-0.1.4/src/tquality_core/pages/base_form.py +42 -0
- tquality_py_core-0.1.4/src/tquality_core/py.typed +0 -0
- tquality_py_core-0.1.4/src/tquality_core/schema.py +66 -0
- tquality_py_core-0.1.4/src/tquality_core/services/__init__.py +17 -0
- tquality_py_core-0.1.4/src/tquality_core/services/logger.py +280 -0
- tquality_py_core-0.1.4/src/tquality_core/utils/__init__.py +3 -0
- tquality_py_core-0.1.4/src/tquality_core/utils/string_utils.py +28 -0
- tquality_py_core-0.1.4/tests/__init__.py +0 -0
- tquality_py_core-0.1.4/tests/test_base_element.py +98 -0
- tquality_py_core-0.1.4/tests/test_cli.py +62 -0
- tquality_py_core-0.1.4/tests/test_config.py +180 -0
- tquality_py_core-0.1.4/tests/test_schema.py +77 -0
- tquality_py_core-0.1.4/tests/test_string_utils.py +26 -0
|
@@ -0,0 +1,196 @@
|
|
|
1
|
+
# Руководство для контрибьюторов
|
|
2
|
+
|
|
3
|
+
## Требования
|
|
4
|
+
|
|
5
|
+
- Python 3.12+
|
|
6
|
+
- [uv](https://docs.astral.sh/uv/) для управления окружением и зависимостями
|
|
7
|
+
|
|
8
|
+
## Настройка окружения
|
|
9
|
+
|
|
10
|
+
```bash
|
|
11
|
+
uv sync
|
|
12
|
+
```
|
|
13
|
+
|
|
14
|
+
Команда создаст `.venv/` и установит зависимости проекта плюс dev-группу
|
|
15
|
+
(mypy и др.).
|
|
16
|
+
|
|
17
|
+
## Установка git-хуков
|
|
18
|
+
|
|
19
|
+
Для автоматической проверки типов mypy перед каждым коммитом выполните:
|
|
20
|
+
|
|
21
|
+
```bash
|
|
22
|
+
./scripts/install-hooks.sh
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
Скрипт установит pre-commit хук, который запускает `uv run mypy` и блокирует
|
|
26
|
+
коммит при ошибках типов.
|
|
27
|
+
|
|
28
|
+
## Стиль кода
|
|
29
|
+
|
|
30
|
+
- Все комментарии, docstring, сообщения логов - на русском языке.
|
|
31
|
+
- Не используйте m-тире (длинное тире). Используйте обычное тире или
|
|
32
|
+
переформулируйте.
|
|
33
|
+
- Не добавляйте строку `Co-Authored-By` в commit-сообщения.
|
|
34
|
+
|
|
35
|
+
## Формат commit-сообщений
|
|
36
|
+
|
|
37
|
+
Каждый коммит начинается с одного или нескольких тегов в квадратных скобках
|
|
38
|
+
(на английском), затем краткое описание на русском языке.
|
|
39
|
+
|
|
40
|
+
### Доступные теги
|
|
41
|
+
|
|
42
|
+
- `[{module}]` - название затронутого модуля: `[Config]`, `[Logger]`, `[BaseForm]`, `[BaseElement]`, `[StringUtils]`, `[CI]`
|
|
43
|
+
- `[Docs]` - изменения документации (README, CONTRIBUTING, docstring'и)
|
|
44
|
+
- `[Fix]` - исправление бага без привязки к issue
|
|
45
|
+
- `[Fix #{issueId}]` - исправление бага по конкретному issue, например `[Fix #42]`
|
|
46
|
+
- `[Style]` - только форматирование, без изменения логики (whitespace, импорты)
|
|
47
|
+
- `[Feature]` - новая функциональность
|
|
48
|
+
|
|
49
|
+
### Примеры
|
|
50
|
+
|
|
51
|
+
```
|
|
52
|
+
[Logger] Имена файлов логов на основе pytest node_id
|
|
53
|
+
[Config][Feature] Поддержка config.json на уровне workspace
|
|
54
|
+
[Fix #12] Исправлен stale element в type_text
|
|
55
|
+
[Docs] Обновлен CONTRIBUTING с процессом релиза
|
|
56
|
+
[BaseElement][Style] Упорядочены объявления абстрактных методов
|
|
57
|
+
[CI][Fix] Unshallow clone перед push'ем в зеркало
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
Теги можно комбинировать, например `[Config][Feature]` или `[BaseForm][Fix]`.
|
|
61
|
+
Теги остаются на английском, чтобы легко фильтровать и автоматизировать.
|
|
62
|
+
|
|
63
|
+
## Проверка типов
|
|
64
|
+
|
|
65
|
+
Проект использует `mypy` в strict-режиме. Перед push'ем проверьте:
|
|
66
|
+
|
|
67
|
+
```bash
|
|
68
|
+
uv run mypy
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
Ошибки типов блокируют merge в master.
|
|
72
|
+
|
|
73
|
+
## Запуск тестов
|
|
74
|
+
|
|
75
|
+
```bash
|
|
76
|
+
uv run pytest -v
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
Тесты запускаются автоматически в CI на каждый MR.
|
|
80
|
+
|
|
81
|
+
## Обновление JSON-схемы
|
|
82
|
+
|
|
83
|
+
Схема `schema/config.schema.json` должна совпадать со схемой, генерируемой
|
|
84
|
+
из `BaseConfig`. Если вы изменили поля `BaseConfig`, обновите схему:
|
|
85
|
+
|
|
86
|
+
```bash
|
|
87
|
+
uv run tquality-config schema
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
Коммит с изменением `BaseConfig` без обновления схемы провалит тест
|
|
91
|
+
`test_committed_schema_matches_base_config` в CI.
|
|
92
|
+
|
|
93
|
+
## Сборка пакета
|
|
94
|
+
|
|
95
|
+
```bash
|
|
96
|
+
uv build
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
Артефакты появятся в `dist/`.
|
|
100
|
+
|
|
101
|
+
## Релиз
|
|
102
|
+
|
|
103
|
+
Версия пакета берется из последнего git-тега вида `vX.Y.Z` через
|
|
104
|
+
`hatch-vcs`. В `pyproject.toml` версия не указывается (поле `dynamic`),
|
|
105
|
+
поэтому рассинхронизация тега и пакета невозможна.
|
|
106
|
+
|
|
107
|
+
Ставьте тег **только на master** (после merge соответствующего MR).
|
|
108
|
+
`mirror-to-github` публикует на GitHub именно то, что на master, и
|
|
109
|
+
проверяет, что коммит тега достижим из master. Тег на feature-ветке
|
|
110
|
+
провалит зеркалирование.
|
|
111
|
+
|
|
112
|
+
```bash
|
|
113
|
+
git checkout master
|
|
114
|
+
git pull
|
|
115
|
+
git tag -a v0.2.0 -m "v0.2.0"
|
|
116
|
+
git push origin v0.2.0
|
|
117
|
+
```
|
|
118
|
+
|
|
119
|
+
Push тега `vX.Y.Z` триггерит три CI-джоба в stage `release`:
|
|
120
|
+
|
|
121
|
+
- **`publish-pypi`** - сборка (`uv build` получает версию из тега через
|
|
122
|
+
`hatch-vcs`) и публикация пакета в публичный
|
|
123
|
+
[PyPI](https://pypi.org/project/tquality-py-core/). Это основной канал
|
|
124
|
+
установки для всех потребителей.
|
|
125
|
+
- **`publish`** - дублирующая публикация в GitLab Package Registry
|
|
126
|
+
(`https://git.tquality.ru/frameworks/python/tquality-py-core/-/packages`)
|
|
127
|
+
как внутреннее зеркало.
|
|
128
|
+
- **`mirror-to-github`** - пушит `master` и сам тег в
|
|
129
|
+
https://github.com/Tquality-ru/tquality-py-core (feature-ветки и
|
|
130
|
+
служебные refs не зеркалируются).
|
|
131
|
+
|
|
132
|
+
### Настройка публикации в PyPI (однократно)
|
|
133
|
+
|
|
134
|
+
1. На https://pypi.org/manage/account/token/ создать API-токен со
|
|
135
|
+
scope, ограниченным проектом `tquality-py-core` (после первой
|
|
136
|
+
ручной публикации). Для самой первой публикации нужен токен с
|
|
137
|
+
глобальным scope.
|
|
138
|
+
2. В GitLab: **Settings → CI/CD → Variables** добавить переменную:
|
|
139
|
+
- Key: `PYPI_TOKEN`
|
|
140
|
+
- Value: токен с PyPI (включая префикс `pypi-`)
|
|
141
|
+
- Protected: yes (только для protected refs, включая теги `v*`)
|
|
142
|
+
- Masked: yes
|
|
143
|
+
|
|
144
|
+
### Установка пакета из GitLab Package Registry (внутренний канал)
|
|
145
|
+
|
|
146
|
+
```bash
|
|
147
|
+
uv pip install tquality-py-core \
|
|
148
|
+
--index-url "https://gitlab-ci-token:${GITLAB_TOKEN}@git.tquality.ru/api/v4/projects/42/packages/pypi/simple"
|
|
149
|
+
```
|
|
150
|
+
|
|
151
|
+
Либо добавьте в `pyproject.toml` консьюмера:
|
|
152
|
+
|
|
153
|
+
```toml
|
|
154
|
+
[[tool.uv.index]]
|
|
155
|
+
name = "tquality"
|
|
156
|
+
url = "https://git.tquality.ru/api/v4/projects/42/packages/pypi/simple"
|
|
157
|
+
explicit = true
|
|
158
|
+
|
|
159
|
+
[tool.uv.sources]
|
|
160
|
+
tquality-py-core = { index = "tquality" }
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
### Настройка зеркалирования в GitHub (однократно)
|
|
164
|
+
|
|
165
|
+
1. Создать GitHub Personal Access Token с правами `public_repo` (или `repo`
|
|
166
|
+
для приватных).
|
|
167
|
+
2. В GitLab: **Settings → CI/CD → Variables** добавить переменную:
|
|
168
|
+
- Key: `GITHUB_MIRROR_TOKEN`
|
|
169
|
+
- Value: токен с GitHub
|
|
170
|
+
- Protected: yes (только для protected refs, включая теги `v*`)
|
|
171
|
+
- Masked: yes
|
|
172
|
+
|
|
173
|
+
Для публикации в Package Registry дополнительная настройка не нужна: джоб
|
|
174
|
+
использует встроенный `CI_JOB_TOKEN`.
|
|
175
|
+
|
|
176
|
+
## Структура репозитория
|
|
177
|
+
|
|
178
|
+
```
|
|
179
|
+
tquality-py-core/
|
|
180
|
+
├── .gitlab-ci.yml # CI: mypy + pytest на MR и master
|
|
181
|
+
├── pyproject.toml # конфиг проекта, mypy, зависимости
|
|
182
|
+
├── scripts/
|
|
183
|
+
│ └── install-hooks.sh # установка git pre-commit хука
|
|
184
|
+
├── schema/
|
|
185
|
+
│ └── config.schema.json # JSON-схема BaseConfig (публикуется через jsDelivr)
|
|
186
|
+
├── src/tquality_core/
|
|
187
|
+
│ ├── cli.py # CLI: tquality-config init / schema
|
|
188
|
+
│ ├── config.py # BaseConfig
|
|
189
|
+
│ ├── schema.py # генератор JSON-схемы
|
|
190
|
+
│ ├── elements/ # BaseElement (ABC)
|
|
191
|
+
│ ├── pages/ # BaseForm
|
|
192
|
+
│ ├── services/ # Logger, step, ScreenshotProvider
|
|
193
|
+
│ └── utils/ # StringUtils
|
|
194
|
+
├── tests/ # pytest тесты
|
|
195
|
+
└── README.md
|
|
196
|
+
```
|
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for describing the origin of the Work and
|
|
141
|
+
reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Support. While redistributing the Work or
|
|
166
|
+
Derivative Works thereof, You may choose to offer, and charge a
|
|
167
|
+
fee for, acceptance of support, warranty, indemnity, or other
|
|
168
|
+
liability obligations and/or rights consistent with this License.
|
|
169
|
+
However, in accepting such obligations, You may act only on Your
|
|
170
|
+
own behalf and on Your sole responsibility, not on behalf of any
|
|
171
|
+
other Contributor, and only if You agree to indemnify, defend,
|
|
172
|
+
and hold each Contributor harmless for any liability incurred by,
|
|
173
|
+
or claims asserted against, such Contributor by reason of your
|
|
174
|
+
accepting any such warranty or support.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright 2026 ООО «Точка качества»
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
|
@@ -0,0 +1,185 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: tquality-py-core
|
|
3
|
+
Version: 0.1.4
|
|
4
|
+
Summary: Driver-agnostic core for tquality test automation (Selenium, Appium, WinAppDriver, etc.)
|
|
5
|
+
Project-URL: Homepage, https://github.com/Tquality-ru/tquality-py-core
|
|
6
|
+
Project-URL: Repository, https://github.com/Tquality-ru/tquality-py-core
|
|
7
|
+
Project-URL: Issues, https://github.com/Tquality-ru/tquality-py-core/issues
|
|
8
|
+
Project-URL: Changelog, https://github.com/Tquality-ru/tquality-py-core/blob/master/CHANGELOG.md
|
|
9
|
+
Author: ООО «Точка качества»
|
|
10
|
+
License-Expression: Apache-2.0
|
|
11
|
+
License-File: LICENSE
|
|
12
|
+
License-File: NOTICE
|
|
13
|
+
Keywords: allure,appium,page-object,qa,selenium,test-automation,testing,tquality,winappdriver
|
|
14
|
+
Classifier: Development Status :: 4 - Beta
|
|
15
|
+
Classifier: Intended Audience :: Developers
|
|
16
|
+
Classifier: Operating System :: OS Independent
|
|
17
|
+
Classifier: Programming Language :: Python
|
|
18
|
+
Classifier: Programming Language :: Python :: 3
|
|
19
|
+
Classifier: Programming Language :: Python :: 3 :: Only
|
|
20
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
21
|
+
Classifier: Topic :: Software Development :: Quality Assurance
|
|
22
|
+
Classifier: Topic :: Software Development :: Testing
|
|
23
|
+
Classifier: Typing :: Typed
|
|
24
|
+
Requires-Python: >=3.12
|
|
25
|
+
Requires-Dist: allure-python-commons>=2.13
|
|
26
|
+
Requires-Dist: dependency-injector>=4.41
|
|
27
|
+
Requires-Dist: json5>=0.9
|
|
28
|
+
Requires-Dist: pydantic-settings>=2.0
|
|
29
|
+
Requires-Dist: pydantic>=2.0
|
|
30
|
+
Description-Content-Type: text/markdown
|
|
31
|
+
|
|
32
|
+
# tquality-py-core
|
|
33
|
+
|
|
34
|
+
Независимое от драйвера ядро для автоматизации тестирования tquality. Предоставляет
|
|
35
|
+
основу, на которой строятся пакеты, специфичные для драйверов (Selenium,
|
|
36
|
+
Appium, WinAppDriver).
|
|
37
|
+
|
|
38
|
+
## Компоненты
|
|
39
|
+
|
|
40
|
+
- **`BaseConfig`** - конфигурация на основе pydantic-settings с загрузкой из
|
|
41
|
+
`config.json5` (с поддержкой комментариев и висячих запятых через json5),
|
|
42
|
+
переменных окружения и dotenv. Для добавления полей, специфичных для
|
|
43
|
+
драйвера, используется наследование.
|
|
44
|
+
- **`Logger`, `LogLevel`, `step`** - журналирование в контексте одного теста
|
|
45
|
+
с интеграцией allure. Уровни шагов: `NORMAL`, `CRITICAL` (снимок экрана в
|
|
46
|
+
конце) и `WITH_SCREENCAST` (видеозапись шага через подключаемый поставщик).
|
|
47
|
+
- **`BaseForm`** - базовый класс для страниц и форм (страница - форма с полным
|
|
48
|
+
контекстом).
|
|
49
|
+
- **`BaseElement`** - абстрактный интерфейс, который реализуют элементы,
|
|
50
|
+
специфичные для драйвера.
|
|
51
|
+
- **`StringUtils`** - вспомогательные функции разбора строк.
|
|
52
|
+
|
|
53
|
+
## Не входит в ядро
|
|
54
|
+
|
|
55
|
+
- Конкретная интеграция с драйверами (Selenium, Appium, WinAppDriver) -
|
|
56
|
+
живёт в отдельных пакетах, зависящих от этого ядра.
|
|
57
|
+
- Типы элементов (`Button`, `Input`, `Label` и т. п.) - реализации,
|
|
58
|
+
специфичные для драйвера, живут рядом с интеграцией драйвера.
|
|
59
|
+
- Настройка контейнера внедрения зависимостей - каждый использующий пакет
|
|
60
|
+
собирает свой контейнер через `dependency-injector`, регистрируя службы
|
|
61
|
+
ядра и службы, специфичные для драйвера.
|
|
62
|
+
|
|
63
|
+
## Контракт интеграции
|
|
64
|
+
|
|
65
|
+
Использующие пакеты должны:
|
|
66
|
+
|
|
67
|
+
1. Наследовать `BaseConfig` с полями, специфичными для драйвера.
|
|
68
|
+
2. Зарегистрировать функцию получения `Logger` через
|
|
69
|
+
`set_logger_resolver(lambda: YourServices.logger())`, где `YourServices` -
|
|
70
|
+
контейнер использующего пакета. Это нужно, чтобы `step()` из ядра
|
|
71
|
+
находил активный `Logger` в любом модуле.
|
|
72
|
+
3. При необходимости реализовать `ScreenshotProvider` / `ScreencastProvider`
|
|
73
|
+
и внедрить их в `Logger` через контейнер, чтобы шаги уровня `CRITICAL`
|
|
74
|
+
прикрепляли снимки экрана, а `WITH_SCREENCAST` - видеозапись (конкретный
|
|
75
|
+
формат - на стороне поставщика, например webm в Selenium) к отчёту
|
|
76
|
+
allure. Без поставщиков шаги проходят с предупреждением в журнал.
|
|
77
|
+
4. Предоставить конкретные подклассы `BaseElement` с логикой поиска и
|
|
78
|
+
ожидания.
|
|
79
|
+
|
|
80
|
+
## Требования
|
|
81
|
+
|
|
82
|
+
- Python 3.12+
|
|
83
|
+
|
|
84
|
+
## Установка
|
|
85
|
+
|
|
86
|
+
Пакет публикуется в [публичный PyPI](https://pypi.org/project/tquality-py-core/).
|
|
87
|
+
Это рекомендуемый способ установки для всех потребителей:
|
|
88
|
+
|
|
89
|
+
```bash
|
|
90
|
+
pip install tquality-py-core
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
или с использованием [uv](https://docs.astral.sh/uv/):
|
|
94
|
+
|
|
95
|
+
```bash
|
|
96
|
+
uv add tquality-py-core
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
В `pyproject.toml` потребителя:
|
|
100
|
+
|
|
101
|
+
```toml
|
|
102
|
+
dependencies = [
|
|
103
|
+
"tquality-py-core>=0.1.3",
|
|
104
|
+
]
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
### Альтернатива: установка из GitHub-зеркала
|
|
108
|
+
|
|
109
|
+
Если нужна сборка из исходников (например, для проверки коммита,
|
|
110
|
+
ещё не вышедшего в релиз), пакет также доступен из публичного
|
|
111
|
+
GitHub-зеркала по тегу:
|
|
112
|
+
|
|
113
|
+
```bash
|
|
114
|
+
uv pip install "tquality-py-core @ git+https://github.com/Tquality-ru/tquality-py-core.git@v0.1.3"
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
В этом случае hatch у потребителя требует явного разрешения
|
|
118
|
+
`direct-references`:
|
|
119
|
+
|
|
120
|
+
```toml
|
|
121
|
+
[tool.hatch.metadata]
|
|
122
|
+
allow-direct-references = true
|
|
123
|
+
```
|
|
124
|
+
|
|
125
|
+
## CLI
|
|
126
|
+
|
|
127
|
+
После установки доступна команда `tquality-config`:
|
|
128
|
+
|
|
129
|
+
```bash
|
|
130
|
+
tquality-config init # сгенерировать config.json5 со значениями по умолчанию
|
|
131
|
+
tquality-config schema # сгенерировать schema/config.schema.json (для сопровождающих)
|
|
132
|
+
```
|
|
133
|
+
|
|
134
|
+
Сгенерированный `config.json5` включает ссылку на JSON-схему, опубликованную
|
|
135
|
+
через jsDelivr. Адрес автоматически привязан к версии пакета: при установке
|
|
136
|
+
выпущенной версии (`0.1.3`) → `@v0.1.3`, при установке невыпущенной версии
|
|
137
|
+
(`+g...`, `.dev`) → `@master`:
|
|
138
|
+
|
|
139
|
+
```jsonc
|
|
140
|
+
{
|
|
141
|
+
"$schema": "https://cdn.jsdelivr.net/gh/Tquality-ru/tquality-py-core@v0.1.3/schema/config.schema.json",
|
|
142
|
+
// Комментарии поддерживаются - можно пояснить выбор значения.
|
|
143
|
+
"base_url": "http://localhost",
|
|
144
|
+
"default_timeout": 10.0,
|
|
145
|
+
"log_dir": "logs",
|
|
146
|
+
"highlight_elements": false,
|
|
147
|
+
}
|
|
148
|
+
```
|
|
149
|
+
|
|
150
|
+
Редакторы с поддержкой JSON Schema (VS Code, JetBrains IDE) автоматически
|
|
151
|
+
подсказывают доступные поля и проверяют значения. Синтаксис jsonc/json5
|
|
152
|
+
позволяет оставлять комментарии `//` и `/* */` и висячие запятые.
|
|
153
|
+
|
|
154
|
+
## Разработка
|
|
155
|
+
|
|
156
|
+
См. [CONTRIBUTING.md](CONTRIBUTING.md) для инструкций по настройке окружения
|
|
157
|
+
разработчика, установке перехватчиков git и проверке типов mypy.
|
|
158
|
+
|
|
159
|
+
## CI/CD
|
|
160
|
+
|
|
161
|
+
GitLab CI запускает две проверки на каждом MR и на master:
|
|
162
|
+
|
|
163
|
+
- **`mypy`** - строгий режим проверки типов.
|
|
164
|
+
- **`tests`** - запуск pytest с отчётом JUnit.
|
|
165
|
+
|
|
166
|
+
При публикации тега git вида `vX.Y.Z`:
|
|
167
|
+
|
|
168
|
+
- **`publish-pypi`** - сборка (версия берётся из тега через `hatch-vcs`)
|
|
169
|
+
и загрузка пакета в публичный
|
|
170
|
+
[PyPI](https://pypi.org/project/tquality-py-core/). Требует переменную
|
|
171
|
+
`PYPI_TOKEN` в настройках CI/CD (protected, masked).
|
|
172
|
+
- **`publish`** - дублирующая публикация в GitLab Package Registry
|
|
173
|
+
(внутреннее зеркало).
|
|
174
|
+
- **`mirror-to-github`** - master и сам тег отправляются в
|
|
175
|
+
https://github.com/Tquality-ru/tquality-py-core (ветки `feature/*`
|
|
176
|
+
на зеркало не копируются).
|
|
177
|
+
|
|
178
|
+
История версий - в [CHANGELOG.md](CHANGELOG.md).
|
|
179
|
+
|
|
180
|
+
## Зачем это существует
|
|
181
|
+
|
|
182
|
+
Отделяет универсальные шаблоны (журналирование, объекты страниц, загрузка
|
|
183
|
+
конфигурации) от кода, специфичного для драйвера. Appium и WinAppDriver
|
|
184
|
+
повторно используют ту же модель объектов страниц, отчётность по шагам и
|
|
185
|
+
конвейер конфигурации без обязательной зависимости от Selenium.
|