blob: 6e82972eb7804d65a26e63da2915e5c72c5653c3 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
|
%global _empty_manifest_terminate_build 0
Name: python-qecore
Version: 3.18
Release: 1
Summary: DesktopQE Tool for unified test execution
License: GPLv3
URL: https://gitlab.com/dogtail/qecore
Source0: https://mirrors.aliyun.com/pypi/web/packages/a1/30/bcc8b685721ffbd778787d96b9e46bf986297f6aa52500b9ec4d17d6d7fc/qecore-3.18.tar.gz
BuildArch: noarch
Requires: python3-behave
Requires: python3-behave-html-formatter
Requires: python3-behave-html-pretty-formatter
Requires: python3-dasbus
Requires: python3-termcolor
%description
## qecore
[](https://gitlab.com/dogtail/qecore/-/pipelines) [](https://pypi.org/project/qecore/)
The future goal for qecore is for it to become project template for automation testing.
As of now the qecore provides a lot of quality of life features for GNOME Desktop testing.
It can be described as a sandbox of sorts for test execution.
Paired with behave and dogtail this project serves as a useful tool for test execution with minimal required setup.
[Project Documentation in gitlab Pages](https://dogtail.gitlab.io/qecore/index.html) - build by CI pipelines on every change
### Execute unit tests
Execute the tests (from the project root directory) on machine with dogtail:
```bash
rm -f /tmp/qecore_version_status.txt
rm -f dist/*.whl
python3 -m build
python3 -m pip install --force-reinstall --upgrade dist/qecore*.whl
sudo -u test scripts/qecore-headless "behave -f html-pretty -o /tmp/report_qecore.html -f plain tests/features"
```
You can use `-f pretty` instead of `-f plain` to get colored output.
The standard output should not contain any python traceback, produced HTML should be complete (after first scenario there is `Status`).
%package -n python3-qecore
Summary: DesktopQE Tool for unified test execution
Provides: python-qecore
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-qecore
## qecore
[](https://gitlab.com/dogtail/qecore/-/pipelines) [](https://pypi.org/project/qecore/)
The future goal for qecore is for it to become project template for automation testing.
As of now the qecore provides a lot of quality of life features for GNOME Desktop testing.
It can be described as a sandbox of sorts for test execution.
Paired with behave and dogtail this project serves as a useful tool for test execution with minimal required setup.
[Project Documentation in gitlab Pages](https://dogtail.gitlab.io/qecore/index.html) - build by CI pipelines on every change
### Execute unit tests
Execute the tests (from the project root directory) on machine with dogtail:
```bash
rm -f /tmp/qecore_version_status.txt
rm -f dist/*.whl
python3 -m build
python3 -m pip install --force-reinstall --upgrade dist/qecore*.whl
sudo -u test scripts/qecore-headless "behave -f html-pretty -o /tmp/report_qecore.html -f plain tests/features"
```
You can use `-f pretty` instead of `-f plain` to get colored output.
The standard output should not contain any python traceback, produced HTML should be complete (after first scenario there is `Status`).
%package help
Summary: Development documents and examples for qecore
Provides: python3-qecore-doc
%description help
## qecore
[](https://gitlab.com/dogtail/qecore/-/pipelines) [](https://pypi.org/project/qecore/)
The future goal for qecore is for it to become project template for automation testing.
As of now the qecore provides a lot of quality of life features for GNOME Desktop testing.
It can be described as a sandbox of sorts for test execution.
Paired with behave and dogtail this project serves as a useful tool for test execution with minimal required setup.
[Project Documentation in gitlab Pages](https://dogtail.gitlab.io/qecore/index.html) - build by CI pipelines on every change
### Execute unit tests
Execute the tests (from the project root directory) on machine with dogtail:
```bash
rm -f /tmp/qecore_version_status.txt
rm -f dist/*.whl
python3 -m build
python3 -m pip install --force-reinstall --upgrade dist/qecore*.whl
sudo -u test scripts/qecore-headless "behave -f html-pretty -o /tmp/report_qecore.html -f plain tests/features"
```
You can use `-f pretty` instead of `-f plain` to get colored output.
The standard output should not contain any python traceback, produced HTML should be complete (after first scenario there is `Status`).
%prep
%autosetup -n qecore-3.18
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "\"/%h/%f.gz\"\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-qecore -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Fri Jun 09 2023 Python_Bot <Python_Bot@openeuler.org> - 3.18-1
- Package Spec generated
|
