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
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
|
%global _empty_manifest_terminate_build 0
Name: python-pytest-regtest
Version: 1.5.0
Release: 1
Summary: pytest plugin for regression tests
License: https://opensource.org/licenses/MIT
URL: https://gitlab.com/uweschmitt/pytest-regtest
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/52/0f/790ba30a32b6f6ab9db946cf39dc72a4cb8ad6d275bc4c3de082e247721f/pytest-regtest-1.5.0.tar.gz
BuildArch: noarch
%description
pytest-regtest is a *pytest*-plugin for implementing regression tests.
Compared to functional testing a regression test does not test if
software produces correct results, instead a regression test checks if
software behaves the same way as it did before introduced changes.
More about regression testing at
<https://en.wikipedia.org/wiki/Regression_testing>. Regression testing
is a common technique to get started when refactoring legacy code
lacking a test suite.
*pytest-regtest* allows capturing selected output which then can be
compared to the captured output from former runs.
To install and activate this plugin execute:
$ pip install pytest-regtest
*pytest-regtest* plugin provides a fixture named *regtest* which can be
used as a file handle for recording data:
```python
def test_squares_up_to_ten(regtest):
result = [i*i for i in range(10)]
# one way to record output:
print(result, file=regtest)
# alternative method to record output:
regtest.write("done")
# or using a context manager:
with regtest:
print("this will be recorded")
```
If you run this test script with *pytest* the first time there is no
recorded output for this test function so far and thus the test will
fail with a message including a diff:
$ py.test
regression test output differences for test_demo.py::test_squares_up_to_ten:
> --- current
> +++ tobe
> @@ -1,2 +1 @@
> -[0, 1, 4, 9, 16, 25, 36, 49, 64, 81]
> -done
> +
The output tells us what the current output is, and that the "tobe" output
is still empty.
For accepting this output, we run *pytest* with the *--reset-regtest*
flag:
$ py.test --regtest-reset
Now the next execution of *py.test* will succeed:
$ py.test
Now we break the test by modifying the code under test to compute the first
eleven square numbers:
```python
from __future__ import print_function
def test_squares_up_to_ten(regtest):
result = [i*i for i in range(11)] # changed !
# one way to record output:
print(result, file=regtest)
# alternative method to record output:
regtest.write("done")
```
The next run of pytest delivers a nice diff of the current and expected output
from this test function:
$ py.test
> --- current
> +++ tobe
> @@ -1,2 +1,2 @@
> -[0, 1, 4, 9, 16, 25, 36, 49, 64, 81, 100]
> +[0, 1, 4, 9, 16, 25, 36, 49, 64, 81]
> done
The recorded output was written to files in the subfolder
`_regtest_outputs` next to your test script(s). You might keep this
folder under version control.
%package -n python3-pytest-regtest
Summary: pytest plugin for regression tests
Provides: python-pytest-regtest
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-pytest-regtest
pytest-regtest is a *pytest*-plugin for implementing regression tests.
Compared to functional testing a regression test does not test if
software produces correct results, instead a regression test checks if
software behaves the same way as it did before introduced changes.
More about regression testing at
<https://en.wikipedia.org/wiki/Regression_testing>. Regression testing
is a common technique to get started when refactoring legacy code
lacking a test suite.
*pytest-regtest* allows capturing selected output which then can be
compared to the captured output from former runs.
To install and activate this plugin execute:
$ pip install pytest-regtest
*pytest-regtest* plugin provides a fixture named *regtest* which can be
used as a file handle for recording data:
```python
def test_squares_up_to_ten(regtest):
result = [i*i for i in range(10)]
# one way to record output:
print(result, file=regtest)
# alternative method to record output:
regtest.write("done")
# or using a context manager:
with regtest:
print("this will be recorded")
```
If you run this test script with *pytest* the first time there is no
recorded output for this test function so far and thus the test will
fail with a message including a diff:
$ py.test
regression test output differences for test_demo.py::test_squares_up_to_ten:
> --- current
> +++ tobe
> @@ -1,2 +1 @@
> -[0, 1, 4, 9, 16, 25, 36, 49, 64, 81]
> -done
> +
The output tells us what the current output is, and that the "tobe" output
is still empty.
For accepting this output, we run *pytest* with the *--reset-regtest*
flag:
$ py.test --regtest-reset
Now the next execution of *py.test* will succeed:
$ py.test
Now we break the test by modifying the code under test to compute the first
eleven square numbers:
```python
from __future__ import print_function
def test_squares_up_to_ten(regtest):
result = [i*i for i in range(11)] # changed !
# one way to record output:
print(result, file=regtest)
# alternative method to record output:
regtest.write("done")
```
The next run of pytest delivers a nice diff of the current and expected output
from this test function:
$ py.test
> --- current
> +++ tobe
> @@ -1,2 +1,2 @@
> -[0, 1, 4, 9, 16, 25, 36, 49, 64, 81, 100]
> +[0, 1, 4, 9, 16, 25, 36, 49, 64, 81]
> done
The recorded output was written to files in the subfolder
`_regtest_outputs` next to your test script(s). You might keep this
folder under version control.
%package help
Summary: Development documents and examples for pytest-regtest
Provides: python3-pytest-regtest-doc
%description help
pytest-regtest is a *pytest*-plugin for implementing regression tests.
Compared to functional testing a regression test does not test if
software produces correct results, instead a regression test checks if
software behaves the same way as it did before introduced changes.
More about regression testing at
<https://en.wikipedia.org/wiki/Regression_testing>. Regression testing
is a common technique to get started when refactoring legacy code
lacking a test suite.
*pytest-regtest* allows capturing selected output which then can be
compared to the captured output from former runs.
To install and activate this plugin execute:
$ pip install pytest-regtest
*pytest-regtest* plugin provides a fixture named *regtest* which can be
used as a file handle for recording data:
```python
def test_squares_up_to_ten(regtest):
result = [i*i for i in range(10)]
# one way to record output:
print(result, file=regtest)
# alternative method to record output:
regtest.write("done")
# or using a context manager:
with regtest:
print("this will be recorded")
```
If you run this test script with *pytest* the first time there is no
recorded output for this test function so far and thus the test will
fail with a message including a diff:
$ py.test
regression test output differences for test_demo.py::test_squares_up_to_ten:
> --- current
> +++ tobe
> @@ -1,2 +1 @@
> -[0, 1, 4, 9, 16, 25, 36, 49, 64, 81]
> -done
> +
The output tells us what the current output is, and that the "tobe" output
is still empty.
For accepting this output, we run *pytest* with the *--reset-regtest*
flag:
$ py.test --regtest-reset
Now the next execution of *py.test* will succeed:
$ py.test
Now we break the test by modifying the code under test to compute the first
eleven square numbers:
```python
from __future__ import print_function
def test_squares_up_to_ten(regtest):
result = [i*i for i in range(11)] # changed !
# one way to record output:
print(result, file=regtest)
# alternative method to record output:
regtest.write("done")
```
The next run of pytest delivers a nice diff of the current and expected output
from this test function:
$ py.test
> --- current
> +++ tobe
> @@ -1,2 +1,2 @@
> -[0, 1, 4, 9, 16, 25, 36, 49, 64, 81, 100]
> +[0, 1, 4, 9, 16, 25, 36, 49, 64, 81]
> done
The recorded output was written to files in the subfolder
`_regtest_outputs` next to your test script(s). You might keep this
folder under version control.
%prep
%autosetup -n pytest-regtest-1.5.0
%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-pytest-regtest -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 1.5.0-1
- Package Spec generated
|
