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
|
%global _empty_manifest_terminate_build 0
Name: python-watching-testrunner
Version: 1.2.1
Release: 1
Summary: Automatic test execution on file changes
License: BSD License
URL: https://github.com/tony/watching-testrunner
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/e9/0b/f67167816182b64b0661ed072d87525d26a79f3f3c24fe7c6a71c0a96170/watching_testrunner-1.2.1.tar.gz
BuildArch: noarch
%description
# Why
Because unit testing is even more fun
- when you don't have to switch out of your editor to get feedback from unit tests.
- the shorter the feedback period is till you get feedback from your tests.
I've seen the usefullness toying with rubys autotest command, so I pestered Felix to build something
like this, and after using it for about a two years, I finally got around to packaging it. :-)
In addition to that it's brain dead simple, has no dependencies and is _really_ small.
# Usage
```bash
% watching_testrunner --help
Usage: watching_testrunner [options] [--] command [arguments...]
Options:
-h, --help show this help message and exit
-b BASEPATH, --basepath=BASEPATH
base path to watch for changes
-p WATCH_WILDCARD, --pattern=WATCH_WILDCARD
glob-style pattern for file names to watch
```
# Examples
```bash
$ watching_testrunner nosetests
```
This will run nosetests whenever any python file below the current directory changes
```bash
$ watching_testrunner -- nosetests $NOSETESTS_ARGUMENTS
```
Will run nosetests all the same, but will not try to parse any of the nosetests arguments.
```bash
$ watching_testrunner --basepath foo/bar --pattern="*" nosetests $NOSETESTS_ARGUMENTS
```
This will run nosetests whenever any file below ./foo/bar changes.
```bash
$ watching_testrunner --basepath path/to/js_tests --pattern="*.js" jasmine --console
```
This will run jasmine --console whenever any js file below `./path/to/js_tests` changes (i.e. you
can use the watching testrunner to get auto test execution using any tool for any language)
%package -n python3-watching-testrunner
Summary: Automatic test execution on file changes
Provides: python-watching-testrunner
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-watching-testrunner
# Why
Because unit testing is even more fun
- when you don't have to switch out of your editor to get feedback from unit tests.
- the shorter the feedback period is till you get feedback from your tests.
I've seen the usefullness toying with rubys autotest command, so I pestered Felix to build something
like this, and after using it for about a two years, I finally got around to packaging it. :-)
In addition to that it's brain dead simple, has no dependencies and is _really_ small.
# Usage
```bash
% watching_testrunner --help
Usage: watching_testrunner [options] [--] command [arguments...]
Options:
-h, --help show this help message and exit
-b BASEPATH, --basepath=BASEPATH
base path to watch for changes
-p WATCH_WILDCARD, --pattern=WATCH_WILDCARD
glob-style pattern for file names to watch
```
# Examples
```bash
$ watching_testrunner nosetests
```
This will run nosetests whenever any python file below the current directory changes
```bash
$ watching_testrunner -- nosetests $NOSETESTS_ARGUMENTS
```
Will run nosetests all the same, but will not try to parse any of the nosetests arguments.
```bash
$ watching_testrunner --basepath foo/bar --pattern="*" nosetests $NOSETESTS_ARGUMENTS
```
This will run nosetests whenever any file below ./foo/bar changes.
```bash
$ watching_testrunner --basepath path/to/js_tests --pattern="*.js" jasmine --console
```
This will run jasmine --console whenever any js file below `./path/to/js_tests` changes (i.e. you
can use the watching testrunner to get auto test execution using any tool for any language)
%package help
Summary: Development documents and examples for watching-testrunner
Provides: python3-watching-testrunner-doc
%description help
# Why
Because unit testing is even more fun
- when you don't have to switch out of your editor to get feedback from unit tests.
- the shorter the feedback period is till you get feedback from your tests.
I've seen the usefullness toying with rubys autotest command, so I pestered Felix to build something
like this, and after using it for about a two years, I finally got around to packaging it. :-)
In addition to that it's brain dead simple, has no dependencies and is _really_ small.
# Usage
```bash
% watching_testrunner --help
Usage: watching_testrunner [options] [--] command [arguments...]
Options:
-h, --help show this help message and exit
-b BASEPATH, --basepath=BASEPATH
base path to watch for changes
-p WATCH_WILDCARD, --pattern=WATCH_WILDCARD
glob-style pattern for file names to watch
```
# Examples
```bash
$ watching_testrunner nosetests
```
This will run nosetests whenever any python file below the current directory changes
```bash
$ watching_testrunner -- nosetests $NOSETESTS_ARGUMENTS
```
Will run nosetests all the same, but will not try to parse any of the nosetests arguments.
```bash
$ watching_testrunner --basepath foo/bar --pattern="*" nosetests $NOSETESTS_ARGUMENTS
```
This will run nosetests whenever any file below ./foo/bar changes.
```bash
$ watching_testrunner --basepath path/to/js_tests --pattern="*.js" jasmine --console
```
This will run jasmine --console whenever any js file below `./path/to/js_tests` changes (i.e. you
can use the watching testrunner to get auto test execution using any tool for any language)
%prep
%autosetup -n watching-testrunner-1.2.1
%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-watching-testrunner -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Mon May 29 2023 Python_Bot <Python_Bot@openeuler.org> - 1.2.1-1
- Package Spec generated
|
