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
|
%global _empty_manifest_terminate_build 0
Name: python-expecttest
Version: 0.1.4
Release: 1
Summary: please add a summary manually as the author left a blank one
License: MIT
URL: https://github.com/ezyang/expecttest
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/10/71/4ee70a15dc3235ec01e0083f95a9989b4b6d5dd2083282cc8748a8a07b78/expecttest-0.1.4.tar.gz
BuildArch: noarch
%description
# expecttest [](https://badge.fury.io/py/expecttest)
This library implements expect tests (also known as "golden" tests). Expect
tests are a method of writing tests where instead of hard-coding the expected
output of a test, you run the test to get the output, and the test framework
automatically populates the expected output. If the output of the test changes,
you can rerun the test with the environment variable `EXPECTTEST_ACCEPT=1` to
automatically update the expected output.
Somewhat unusually, this library implements *inline* expect tests: that is to
say, the expected output isn't saved to an external file, it is saved directly
in the Python file (and we modify your Python file when updating the expect
test.)
The general recipe for how to use this is as follows:
1. Write your test and use `assertExpectedInline()` instead of a normal
`assertEqual`. Leave the expected argument blank with an empty string:
```py
self.assertExpectedInline(some_func(), "")
```
2. Run your test. It should fail, and you get an error message about
accepting the output with `EXPECTTEST_ACCEPT=1`
3. Rerun the test with `EXPECTTEST_ACCEPT=1`. Now the previously blank string
literal will contain the expected value of the test.
```py
self.assertExpectedInline(some_func(), "my_value")
```
Some tips and tricks:
- Often, you will want to expect test on a multiline string. This framework
understands triple-quoted strings, so you can just write `"""my_value"""`
and it will turn into triple-quoted strings.
- Take some time thinking about how exactly you want to design the output
format of the expect test. It is often profitable to design an output
representation specifically for expect tests.
%package -n python3-expecttest
Summary: please add a summary manually as the author left a blank one
Provides: python-expecttest
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-expecttest
# expecttest [](https://badge.fury.io/py/expecttest)
This library implements expect tests (also known as "golden" tests). Expect
tests are a method of writing tests where instead of hard-coding the expected
output of a test, you run the test to get the output, and the test framework
automatically populates the expected output. If the output of the test changes,
you can rerun the test with the environment variable `EXPECTTEST_ACCEPT=1` to
automatically update the expected output.
Somewhat unusually, this library implements *inline* expect tests: that is to
say, the expected output isn't saved to an external file, it is saved directly
in the Python file (and we modify your Python file when updating the expect
test.)
The general recipe for how to use this is as follows:
1. Write your test and use `assertExpectedInline()` instead of a normal
`assertEqual`. Leave the expected argument blank with an empty string:
```py
self.assertExpectedInline(some_func(), "")
```
2. Run your test. It should fail, and you get an error message about
accepting the output with `EXPECTTEST_ACCEPT=1`
3. Rerun the test with `EXPECTTEST_ACCEPT=1`. Now the previously blank string
literal will contain the expected value of the test.
```py
self.assertExpectedInline(some_func(), "my_value")
```
Some tips and tricks:
- Often, you will want to expect test on a multiline string. This framework
understands triple-quoted strings, so you can just write `"""my_value"""`
and it will turn into triple-quoted strings.
- Take some time thinking about how exactly you want to design the output
format of the expect test. It is often profitable to design an output
representation specifically for expect tests.
%package help
Summary: Development documents and examples for expecttest
Provides: python3-expecttest-doc
%description help
# expecttest [](https://badge.fury.io/py/expecttest)
This library implements expect tests (also known as "golden" tests). Expect
tests are a method of writing tests where instead of hard-coding the expected
output of a test, you run the test to get the output, and the test framework
automatically populates the expected output. If the output of the test changes,
you can rerun the test with the environment variable `EXPECTTEST_ACCEPT=1` to
automatically update the expected output.
Somewhat unusually, this library implements *inline* expect tests: that is to
say, the expected output isn't saved to an external file, it is saved directly
in the Python file (and we modify your Python file when updating the expect
test.)
The general recipe for how to use this is as follows:
1. Write your test and use `assertExpectedInline()` instead of a normal
`assertEqual`. Leave the expected argument blank with an empty string:
```py
self.assertExpectedInline(some_func(), "")
```
2. Run your test. It should fail, and you get an error message about
accepting the output with `EXPECTTEST_ACCEPT=1`
3. Rerun the test with `EXPECTTEST_ACCEPT=1`. Now the previously blank string
literal will contain the expected value of the test.
```py
self.assertExpectedInline(some_func(), "my_value")
```
Some tips and tricks:
- Often, you will want to expect test on a multiline string. This framework
understands triple-quoted strings, so you can just write `"""my_value"""`
and it will turn into triple-quoted strings.
- Take some time thinking about how exactly you want to design the output
format of the expect test. It is often profitable to design an output
representation specifically for expect tests.
%prep
%autosetup -n expecttest-0.1.4
%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-expecttest -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Mon Apr 10 2023 Python_Bot <Python_Bot@openeuler.org> - 0.1.4-1
- Package Spec generated
|
