summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCoprDistGit <infra@openeuler.org>2023-04-11 06:19:53 +0000
committerCoprDistGit <infra@openeuler.org>2023-04-11 06:19:53 +0000
commitbc6dcf851b3fa3d20e59e22d62df86e2442dc161 (patch)
treed1414ecdb419a9470641e0ee665ee5b9a9712b93
parentf91be58b2357690d1b56c1688caf567b7616fe39 (diff)
automatic import of python-fudge
-rw-r--r--.gitignore1
-rw-r--r--python-fudge.spec147
-rw-r--r--sources1
3 files changed, 149 insertions, 0 deletions
diff --git a/.gitignore b/.gitignore
index e69de29..0e7a48b 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/fudge-1.1.1.tar.gz
diff --git a/python-fudge.spec b/python-fudge.spec
new file mode 100644
index 0000000..5454a44
--- /dev/null
+++ b/python-fudge.spec
@@ -0,0 +1,147 @@
+%global _empty_manifest_terminate_build 0
+Name: python-fudge
+Version: 1.1.1
+Release: 1
+Summary: Replace real objects with fakes (mocks, stubs, etc) while testing.
+License: The MIT License
+URL: https://github.com/fudge-py/fudge
+Source0: https://mirrors.nju.edu.cn/pypi/web/packages/65/71/f44731d536a9b146c5d9a4eb9d3bacd8aae7dbb3597382f3f9bd3d015577/fudge-1.1.1.tar.gz
+BuildArch: noarch
+
+
+%description
+
+Complete documentation is available at https://fudge.readthedocs.org/en/latest/
+
+Fudge is a Python module for using fake objects (mocks and stubs) to test real ones.
+
+In readable Python code, you declare what methods are available on your fake and
+how they should be called. Then you inject that into your application and start
+testing. This declarative approach means you don't have to record and playback
+actions and you don't have to inspect your fakes after running code. If the fake
+object was used incorrectly then you'll see an informative exception message
+with a traceback that points to the culprit.
+
+Here is a quick preview of how you can test code that sends
+email without actually sending email::
+
+ @fudge.patch('smtplib.SMTP')
+ def test_mailer(FakeSMTP):
+ # Declare how the SMTP class should be used:
+ (FakeSMTP.expects_call()
+ .expects('connect')
+ .expects('sendmail').with_arg_count(3))
+ # Run production code:
+ send_mail()
+ # ...expectations are verified automatically at the end of the test
+
+
+
+%package -n python3-fudge
+Summary: Replace real objects with fakes (mocks, stubs, etc) while testing.
+Provides: python-fudge
+BuildRequires: python3-devel
+BuildRequires: python3-setuptools
+BuildRequires: python3-pip
+%description -n python3-fudge
+
+Complete documentation is available at https://fudge.readthedocs.org/en/latest/
+
+Fudge is a Python module for using fake objects (mocks and stubs) to test real ones.
+
+In readable Python code, you declare what methods are available on your fake and
+how they should be called. Then you inject that into your application and start
+testing. This declarative approach means you don't have to record and playback
+actions and you don't have to inspect your fakes after running code. If the fake
+object was used incorrectly then you'll see an informative exception message
+with a traceback that points to the culprit.
+
+Here is a quick preview of how you can test code that sends
+email without actually sending email::
+
+ @fudge.patch('smtplib.SMTP')
+ def test_mailer(FakeSMTP):
+ # Declare how the SMTP class should be used:
+ (FakeSMTP.expects_call()
+ .expects('connect')
+ .expects('sendmail').with_arg_count(3))
+ # Run production code:
+ send_mail()
+ # ...expectations are verified automatically at the end of the test
+
+
+
+%package help
+Summary: Development documents and examples for fudge
+Provides: python3-fudge-doc
+%description help
+
+Complete documentation is available at https://fudge.readthedocs.org/en/latest/
+
+Fudge is a Python module for using fake objects (mocks and stubs) to test real ones.
+
+In readable Python code, you declare what methods are available on your fake and
+how they should be called. Then you inject that into your application and start
+testing. This declarative approach means you don't have to record and playback
+actions and you don't have to inspect your fakes after running code. If the fake
+object was used incorrectly then you'll see an informative exception message
+with a traceback that points to the culprit.
+
+Here is a quick preview of how you can test code that sends
+email without actually sending email::
+
+ @fudge.patch('smtplib.SMTP')
+ def test_mailer(FakeSMTP):
+ # Declare how the SMTP class should be used:
+ (FakeSMTP.expects_call()
+ .expects('connect')
+ .expects('sendmail').with_arg_count(3))
+ # Run production code:
+ send_mail()
+ # ...expectations are verified automatically at the end of the test
+
+
+
+%prep
+%autosetup -n fudge-1.1.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-fudge -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 1.1.1-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..e08fa13
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+3aefdd12c3e0518665fe6735b24a0f9b fudge-1.1.1.tar.gz