diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-logging-test-case.spec | 117 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 119 insertions, 0 deletions
@@ -0,0 +1 @@ +/logging-test-case-1.4.1.tar.gz diff --git a/python-logging-test-case.spec b/python-logging-test-case.spec new file mode 100644 index 0000000..b926060 --- /dev/null +++ b/python-logging-test-case.spec @@ -0,0 +1,117 @@ +%global _empty_manifest_terminate_build 0 +Name: python-logging-test-case +Version: 1.4.1 +Release: 1 +Summary: Provides class LoggingTestCase to help test log files. +License: MIT +URL: https://github.com/chadrosenquist/logging-test-case +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/6e/f7/18cd4bc29887b3c25972167ffba32993c18530b1022a8136e2353631fbf7/logging-test-case-1.4.1.tar.gz +BuildArch: noarch + + +%description +Production systems rely heavily upon logging. Unit tests should verify +logs are correct. ``unittest.assertLogs()`` allows developers to verify +logs are correct. Including this context manager in every test case +becomes tiresome. Also, if the test fails, the logs are not displayed. +This project provides the function decorator ``@capturelogs``. +``@capturelogs`` is similar to ``unittest.assertLogs()``, but it is a +function decorator, reducing the clutter inside the test function. +This project provides the class ``LoggingTestCase``, which inherits from +``unittest.TestCase``. For every test run, logs are automatically +captured to ``self.captured_logs``. If the test fails, the contents of +``self.captured_logs`` are written to the test output for easy +debugging. ``LoggingTestCase`` provides context manager ``assertNoLogs`` +to verify no logs were emitted within the context. +- Use ``@capturelogs`` if only a few tests involve log files. +- Use ``LoggingTestCase`` if most of the tests involve logs. This + avoids putting a function decorator for each function. + +%package -n python3-logging-test-case +Summary: Provides class LoggingTestCase to help test log files. +Provides: python-logging-test-case +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-logging-test-case +Production systems rely heavily upon logging. Unit tests should verify +logs are correct. ``unittest.assertLogs()`` allows developers to verify +logs are correct. Including this context manager in every test case +becomes tiresome. Also, if the test fails, the logs are not displayed. +This project provides the function decorator ``@capturelogs``. +``@capturelogs`` is similar to ``unittest.assertLogs()``, but it is a +function decorator, reducing the clutter inside the test function. +This project provides the class ``LoggingTestCase``, which inherits from +``unittest.TestCase``. For every test run, logs are automatically +captured to ``self.captured_logs``. If the test fails, the contents of +``self.captured_logs`` are written to the test output for easy +debugging. ``LoggingTestCase`` provides context manager ``assertNoLogs`` +to verify no logs were emitted within the context. +- Use ``@capturelogs`` if only a few tests involve log files. +- Use ``LoggingTestCase`` if most of the tests involve logs. This + avoids putting a function decorator for each function. + +%package help +Summary: Development documents and examples for logging-test-case +Provides: python3-logging-test-case-doc +%description help +Production systems rely heavily upon logging. Unit tests should verify +logs are correct. ``unittest.assertLogs()`` allows developers to verify +logs are correct. Including this context manager in every test case +becomes tiresome. Also, if the test fails, the logs are not displayed. +This project provides the function decorator ``@capturelogs``. +``@capturelogs`` is similar to ``unittest.assertLogs()``, but it is a +function decorator, reducing the clutter inside the test function. +This project provides the class ``LoggingTestCase``, which inherits from +``unittest.TestCase``. For every test run, logs are automatically +captured to ``self.captured_logs``. If the test fails, the contents of +``self.captured_logs`` are written to the test output for easy +debugging. ``LoggingTestCase`` provides context manager ``assertNoLogs`` +to verify no logs were emitted within the context. +- Use ``@capturelogs`` if only a few tests involve log files. +- Use ``LoggingTestCase`` if most of the tests involve logs. This + avoids putting a function decorator for each function. + +%prep +%autosetup -n logging-test-case-1.4.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-logging-test-case -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 1.4.1-1 +- Package Spec generated @@ -0,0 +1 @@ +9bb10c66e0ed958acf527d4a6784755b logging-test-case-1.4.1.tar.gz |