automatic import of python-robotsuiteopeneuler20.03

3 files changed, 186 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..0e3a97c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/robotsuite-2.3.1.tar.gz
diff --git a/python-robotsuite.spec b/python-robotsuite.spec
new file mode 100644
index 0000000..9caca69
--- /dev/null
+++ b/python-robotsuite.spec
@@ -0,0 +1,184 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-robotsuite
+Version:	2.3.1
+Release:	1
+Summary:	Robot Framework test suite for Python unittest framework
+License:	GPL version 2
+URL:		https://github.com/collective/robotsuite/
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/a3/4c/2ee987b98e3c9ed1b48f763fd611db80e772a91c814ce17235e3a6be5e35/robotsuite-2.3.1.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-six
+Requires:	python3-setuptools
+Requires:	python3-lxml
+Requires:	python3-robotframework
+
+%description
+This is an experimental package
+for wrapping Robot Framework test suites into Python unittest suites
+to make it possible to run Robot Framework tests
+as `plone.testing`_'s layered test suites:
+    import unittest
+    from plone.testing import layered
+    from robotsuite import RobotTestSuite
+    from my_package.testing import ACCEPTANCE_TESTING
+    def test_suite():
+        suite = unittest.TestSuite()
+        suite.addTests([
+            layered(RobotTestSuite('mysuite.txt'),
+                    layer=ACCEPTANCE_TESTING),
+        ])
+        return suite
+*RobotTestSuite* splits Robot Framework test suites into separate
+unittest test cases so that Robot will be run once for every test
+case in every test suite parsed from the given Robot Framework
+test suite.
+Because of that, each Robot will generate a separate test report
+for each test.
+Each report will have it's own folder,
+which are created recursively
+reflecting the structure of the given test suite.
+*RobotTestSuite*'s way of wrapping tests into
+unittest's test suite is similar to how doctest-module's
+DocTestSuite does its wrappings.
+See the documentation of DocTestSuite for
+possible common parameters (e.g. for how to pass a test suite from a
+different package).
+The main motivation behind this package is to make
+Robot Framework support existing test fixtures and test isolation
+when testing `Plone`_.
+Yet, this should help anyone wanting to use Robot Framework with
+`zope.testrunner`_ or other Python unittest compatible test runner.
+If this works for you, please contribute at:
+http://github.com/collective/robotsuite/
+
+%package -n python3-robotsuite
+Summary:	Robot Framework test suite for Python unittest framework
+Provides:	python-robotsuite
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-robotsuite
+This is an experimental package
+for wrapping Robot Framework test suites into Python unittest suites
+to make it possible to run Robot Framework tests
+as `plone.testing`_'s layered test suites:
+    import unittest
+    from plone.testing import layered
+    from robotsuite import RobotTestSuite
+    from my_package.testing import ACCEPTANCE_TESTING
+    def test_suite():
+        suite = unittest.TestSuite()
+        suite.addTests([
+            layered(RobotTestSuite('mysuite.txt'),
+                    layer=ACCEPTANCE_TESTING),
+        ])
+        return suite
+*RobotTestSuite* splits Robot Framework test suites into separate
+unittest test cases so that Robot will be run once for every test
+case in every test suite parsed from the given Robot Framework
+test suite.
+Because of that, each Robot will generate a separate test report
+for each test.
+Each report will have it's own folder,
+which are created recursively
+reflecting the structure of the given test suite.
+*RobotTestSuite*'s way of wrapping tests into
+unittest's test suite is similar to how doctest-module's
+DocTestSuite does its wrappings.
+See the documentation of DocTestSuite for
+possible common parameters (e.g. for how to pass a test suite from a
+different package).
+The main motivation behind this package is to make
+Robot Framework support existing test fixtures and test isolation
+when testing `Plone`_.
+Yet, this should help anyone wanting to use Robot Framework with
+`zope.testrunner`_ or other Python unittest compatible test runner.
+If this works for you, please contribute at:
+http://github.com/collective/robotsuite/
+
+%package help
+Summary:	Development documents and examples for robotsuite
+Provides:	python3-robotsuite-doc
+%description help
+This is an experimental package
+for wrapping Robot Framework test suites into Python unittest suites
+to make it possible to run Robot Framework tests
+as `plone.testing`_'s layered test suites:
+    import unittest
+    from plone.testing import layered
+    from robotsuite import RobotTestSuite
+    from my_package.testing import ACCEPTANCE_TESTING
+    def test_suite():
+        suite = unittest.TestSuite()
+        suite.addTests([
+            layered(RobotTestSuite('mysuite.txt'),
+                    layer=ACCEPTANCE_TESTING),
+        ])
+        return suite
+*RobotTestSuite* splits Robot Framework test suites into separate
+unittest test cases so that Robot will be run once for every test
+case in every test suite parsed from the given Robot Framework
+test suite.
+Because of that, each Robot will generate a separate test report
+for each test.
+Each report will have it's own folder,
+which are created recursively
+reflecting the structure of the given test suite.
+*RobotTestSuite*'s way of wrapping tests into
+unittest's test suite is similar to how doctest-module's
+DocTestSuite does its wrappings.
+See the documentation of DocTestSuite for
+possible common parameters (e.g. for how to pass a test suite from a
+different package).
+The main motivation behind this package is to make
+Robot Framework support existing test fixtures and test isolation
+when testing `Plone`_.
+Yet, this should help anyone wanting to use Robot Framework with
+`zope.testrunner`_ or other Python unittest compatible test runner.
+If this works for you, please contribute at:
+http://github.com/collective/robotsuite/
+
+%prep
+%autosetup -n robotsuite-2.3.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-robotsuite -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 2.3.1-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..d51ab56
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+1a0b6e17c0a6d2257f09716699fb9f78  robotsuite-2.3.1.tar.gz