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
|
%global _empty_manifest_terminate_build 0
Name: python-pycotap
Version: 1.2.2
Release: 1
Summary: A tiny test runner that outputs TAP results to standard output.
License: MIT
URL: https://el-tramo.be/pycotap
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/5c/c0/62b2c4749c380b20e9cd8a4729b32d2ac99fac0540c026a4c9347a1a546f/pycotap-1.2.2.tar.gz
BuildArch: noarch
%description
`pycotap` is a simple Python test runner for ``unittest`` that outputs
`Test Anything Protocol <http://testanything.org>`_ results directly to standard output.
Contrary to other TAP runners for Python, ``pycotap`` ...
- ... prints TAP (and *only* TAP) to standard output instead of to a separate file,
allowing you to pipe it directly to TAP pretty printers and processors
(such as the ones listed on
`the tape page <https://www.npmjs.com/package/tape#pretty-reporters>`_). By
piping it to other consumers, you can avoid the need to add
specific test runners to your test code. Since the TAP results
are printed as they come in, the consumers can directly display results while
the tests are run.
- ... only contains a TAP reporter, so no parsers, no frameworks, no dependencies, ...
- ... is configurable: you can choose how you want the test output and test result
diagnostics to end up in your TAP output (as TAP diagnostics, YAML blocks, or
attachments). The defaults are optimized for a `Jenkins <http://jenkins-ci.org>`_ based
flow.
Documentation and examples can be found on `the pycotap page
<https://el-tramo.be/pycotap>`_.
%package -n python3-pycotap
Summary: A tiny test runner that outputs TAP results to standard output.
Provides: python-pycotap
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-pycotap
`pycotap` is a simple Python test runner for ``unittest`` that outputs
`Test Anything Protocol <http://testanything.org>`_ results directly to standard output.
Contrary to other TAP runners for Python, ``pycotap`` ...
- ... prints TAP (and *only* TAP) to standard output instead of to a separate file,
allowing you to pipe it directly to TAP pretty printers and processors
(such as the ones listed on
`the tape page <https://www.npmjs.com/package/tape#pretty-reporters>`_). By
piping it to other consumers, you can avoid the need to add
specific test runners to your test code. Since the TAP results
are printed as they come in, the consumers can directly display results while
the tests are run.
- ... only contains a TAP reporter, so no parsers, no frameworks, no dependencies, ...
- ... is configurable: you can choose how you want the test output and test result
diagnostics to end up in your TAP output (as TAP diagnostics, YAML blocks, or
attachments). The defaults are optimized for a `Jenkins <http://jenkins-ci.org>`_ based
flow.
Documentation and examples can be found on `the pycotap page
<https://el-tramo.be/pycotap>`_.
%package help
Summary: Development documents and examples for pycotap
Provides: python3-pycotap-doc
%description help
`pycotap` is a simple Python test runner for ``unittest`` that outputs
`Test Anything Protocol <http://testanything.org>`_ results directly to standard output.
Contrary to other TAP runners for Python, ``pycotap`` ...
- ... prints TAP (and *only* TAP) to standard output instead of to a separate file,
allowing you to pipe it directly to TAP pretty printers and processors
(such as the ones listed on
`the tape page <https://www.npmjs.com/package/tape#pretty-reporters>`_). By
piping it to other consumers, you can avoid the need to add
specific test runners to your test code. Since the TAP results
are printed as they come in, the consumers can directly display results while
the tests are run.
- ... only contains a TAP reporter, so no parsers, no frameworks, no dependencies, ...
- ... is configurable: you can choose how you want the test output and test result
diagnostics to end up in your TAP output (as TAP diagnostics, YAML blocks, or
attachments). The defaults are optimized for a `Jenkins <http://jenkins-ci.org>`_ based
flow.
Documentation and examples can be found on `the pycotap page
<https://el-tramo.be/pycotap>`_.
%prep
%autosetup -n pycotap-1.2.2
%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-pycotap -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Thu Mar 09 2023 Python_Bot <Python_Bot@openeuler.org> - 1.2.2-1
- Package Spec generated
|
