automatic import of python-robotframework-seleniumtestability

3 files changed, 275 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..018fe57 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/robotframework-seleniumtestability-2.1.0.tar.gz
diff --git a/python-robotframework-seleniumtestability.spec b/python-robotframework-seleniumtestability.spec
new file mode 100644
index 0000000..9fb1a54
--- /dev/null
+++ b/python-robotframework-seleniumtestability.spec
@@ -0,0 +1,273 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-robotframework-seleniumtestability
+Version:	2.1.0
+Release:	1
+Summary:	SeleniumTestability library that helps speed up tests withasyncronous evens
+License:	Apache License 2.0
+URL:		https://github.com/marketsquare/robotframework-seleniumtestability
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/ce/63/1e1c64311859c4ea6817acf8bf1f6635d01517d2e79e4496457e961bc921/robotframework-seleniumtestability-2.1.0.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-robotframework-seleniumlibrary
+Requires:	python3-furl
+Requires:	python3-wrapt
+
+%description
+SeleniumTestability is a plugin to Robot Framework's SeleniumLibrary that adds
+functionality to it doesn't fit into its mission. These new features are archived
+by SL's plugin api that then automatically instrumentents the web application via
+javascript calls and provides  keywords to bridge those into Robot Framework.
+Plugin provides automatic detection of asyncronous events happening within
+the web application. For example, if a rest api is called from the application,
+testcase can automatically wait for that call to finish before doing any
+interaction in the UI. There's also a bunch of functionality like fetching of
+browser logs,  keywords to interact with local and session storage.  See the
+keyword documentation [here](https://marketsquare.github.io/robotframework-seleniumtestability/index.html?tag=plugin)
+for more details.
+SeleniumTestability relies on core Selenium's feature EventFiringWebdriver
+and provides it's own listener interface that takes care of waiting in right
+places and instrumenting the SUT whenever it is needed.
+In the future, its also possible to extend the javascript parts of
+SeleniumTestability to incorporate more state inspections.
+Monitoring of the asyncronous events is archived with help of [Testability.js](https://github.com/alfonso-presa/testability.js)
+and its [bindings](https://github.com/alfonso-presa/testability-browser-bindings)
+# Support
+"Official" support channel available in [Gitter.im](https://gitter.im/robotframework-seleniumtestability/community)
+# Installation
+```
+pip install robotframework-seleniumtestability
+```
+# Usage
+## Initialize library
+```
+Library         SeleniumLibrary     plugins=SeleniumTestability;True;30 Seconds;True
+```
+For parameter descriptions, refer to keyword docmentation.
+## Example
+```robotframework
+  Click Element             id:button_that_triggers_ajax_request
+  Click Element             id:some_other_element
+  Log To Console            This will happen right after clicking
+```
+In here, if automatic_wait has been enabled, second `Click Element` keyword wont
+be executed before action triggered by the first button is finished.
+If automatic_wait is not enabled, test case can request the wait itself and previous
+example would look something like this.
+```
+  Click Element               id:button_that_triggers_ajax_request
+  Wait For Testability Ready
+  Click Element               id:some_other_element
+  Wait For Testability Ready
+  Log To Console              This would show after events triggered by second click are done.
+```
+# Currently Supported Asyncronous features
+* setTimeout & setImmediate calls and wait for them.
+* fetch() call and wait for it to finish
+* XHR requests and wait for them to finish
+* CSS Animations and wait form them to finish
+* CSS Transitions and wait form them to finish
+* Viewport scrolling.
+Do note that catching css animations and transitions is browser dependant. In the past
+certain browsers did not implement these features as "the standard" would require.
+# Other functionality.
+SeleniumTestability also provides other conveniance keywords that do not make sense to incorporate into
+SeleniumLibrary itself, mainly due to functionality not being in scope of SeleniumLibrary and Selenium
+python bindings. Do check the keyword documentation for up to date list of keywords.
+# Keyword Documentation
+Keyword documentation [here](https://marketsquare.github.io/robotframework-seleniumtestability/index.html?tag=plugin) and if you need to create one for offline usage:
+```
+python -m robot.libdoc SeleniumLibrary::plugins=SeleniumTestability
+```
+# Contributing
+[CONTRIBUTING.md](https://github.com/marketsquare/robotframework-seleniumtestability/blob/master/CONTRIBUTING.md) documents how to setup the environment for further development of SeleniumTestability.
+
+%package -n python3-robotframework-seleniumtestability
+Summary:	SeleniumTestability library that helps speed up tests withasyncronous evens
+Provides:	python-robotframework-seleniumtestability
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-robotframework-seleniumtestability
+SeleniumTestability is a plugin to Robot Framework's SeleniumLibrary that adds
+functionality to it doesn't fit into its mission. These new features are archived
+by SL's plugin api that then automatically instrumentents the web application via
+javascript calls and provides  keywords to bridge those into Robot Framework.
+Plugin provides automatic detection of asyncronous events happening within
+the web application. For example, if a rest api is called from the application,
+testcase can automatically wait for that call to finish before doing any
+interaction in the UI. There's also a bunch of functionality like fetching of
+browser logs,  keywords to interact with local and session storage.  See the
+keyword documentation [here](https://marketsquare.github.io/robotframework-seleniumtestability/index.html?tag=plugin)
+for more details.
+SeleniumTestability relies on core Selenium's feature EventFiringWebdriver
+and provides it's own listener interface that takes care of waiting in right
+places and instrumenting the SUT whenever it is needed.
+In the future, its also possible to extend the javascript parts of
+SeleniumTestability to incorporate more state inspections.
+Monitoring of the asyncronous events is archived with help of [Testability.js](https://github.com/alfonso-presa/testability.js)
+and its [bindings](https://github.com/alfonso-presa/testability-browser-bindings)
+# Support
+"Official" support channel available in [Gitter.im](https://gitter.im/robotframework-seleniumtestability/community)
+# Installation
+```
+pip install robotframework-seleniumtestability
+```
+# Usage
+## Initialize library
+```
+Library         SeleniumLibrary     plugins=SeleniumTestability;True;30 Seconds;True
+```
+For parameter descriptions, refer to keyword docmentation.
+## Example
+```robotframework
+  Click Element             id:button_that_triggers_ajax_request
+  Click Element             id:some_other_element
+  Log To Console            This will happen right after clicking
+```
+In here, if automatic_wait has been enabled, second `Click Element` keyword wont
+be executed before action triggered by the first button is finished.
+If automatic_wait is not enabled, test case can request the wait itself and previous
+example would look something like this.
+```
+  Click Element               id:button_that_triggers_ajax_request
+  Wait For Testability Ready
+  Click Element               id:some_other_element
+  Wait For Testability Ready
+  Log To Console              This would show after events triggered by second click are done.
+```
+# Currently Supported Asyncronous features
+* setTimeout & setImmediate calls and wait for them.
+* fetch() call and wait for it to finish
+* XHR requests and wait for them to finish
+* CSS Animations and wait form them to finish
+* CSS Transitions and wait form them to finish
+* Viewport scrolling.
+Do note that catching css animations and transitions is browser dependant. In the past
+certain browsers did not implement these features as "the standard" would require.
+# Other functionality.
+SeleniumTestability also provides other conveniance keywords that do not make sense to incorporate into
+SeleniumLibrary itself, mainly due to functionality not being in scope of SeleniumLibrary and Selenium
+python bindings. Do check the keyword documentation for up to date list of keywords.
+# Keyword Documentation
+Keyword documentation [here](https://marketsquare.github.io/robotframework-seleniumtestability/index.html?tag=plugin) and if you need to create one for offline usage:
+```
+python -m robot.libdoc SeleniumLibrary::plugins=SeleniumTestability
+```
+# Contributing
+[CONTRIBUTING.md](https://github.com/marketsquare/robotframework-seleniumtestability/blob/master/CONTRIBUTING.md) documents how to setup the environment for further development of SeleniumTestability.
+
+%package help
+Summary:	Development documents and examples for robotframework-seleniumtestability
+Provides:	python3-robotframework-seleniumtestability-doc
+%description help
+SeleniumTestability is a plugin to Robot Framework's SeleniumLibrary that adds
+functionality to it doesn't fit into its mission. These new features are archived
+by SL's plugin api that then automatically instrumentents the web application via
+javascript calls and provides  keywords to bridge those into Robot Framework.
+Plugin provides automatic detection of asyncronous events happening within
+the web application. For example, if a rest api is called from the application,
+testcase can automatically wait for that call to finish before doing any
+interaction in the UI. There's also a bunch of functionality like fetching of
+browser logs,  keywords to interact with local and session storage.  See the
+keyword documentation [here](https://marketsquare.github.io/robotframework-seleniumtestability/index.html?tag=plugin)
+for more details.
+SeleniumTestability relies on core Selenium's feature EventFiringWebdriver
+and provides it's own listener interface that takes care of waiting in right
+places and instrumenting the SUT whenever it is needed.
+In the future, its also possible to extend the javascript parts of
+SeleniumTestability to incorporate more state inspections.
+Monitoring of the asyncronous events is archived with help of [Testability.js](https://github.com/alfonso-presa/testability.js)
+and its [bindings](https://github.com/alfonso-presa/testability-browser-bindings)
+# Support
+"Official" support channel available in [Gitter.im](https://gitter.im/robotframework-seleniumtestability/community)
+# Installation
+```
+pip install robotframework-seleniumtestability
+```
+# Usage
+## Initialize library
+```
+Library         SeleniumLibrary     plugins=SeleniumTestability;True;30 Seconds;True
+```
+For parameter descriptions, refer to keyword docmentation.
+## Example
+```robotframework
+  Click Element             id:button_that_triggers_ajax_request
+  Click Element             id:some_other_element
+  Log To Console            This will happen right after clicking
+```
+In here, if automatic_wait has been enabled, second `Click Element` keyword wont
+be executed before action triggered by the first button is finished.
+If automatic_wait is not enabled, test case can request the wait itself and previous
+example would look something like this.
+```
+  Click Element               id:button_that_triggers_ajax_request
+  Wait For Testability Ready
+  Click Element               id:some_other_element
+  Wait For Testability Ready
+  Log To Console              This would show after events triggered by second click are done.
+```
+# Currently Supported Asyncronous features
+* setTimeout & setImmediate calls and wait for them.
+* fetch() call and wait for it to finish
+* XHR requests and wait for them to finish
+* CSS Animations and wait form them to finish
+* CSS Transitions and wait form them to finish
+* Viewport scrolling.
+Do note that catching css animations and transitions is browser dependant. In the past
+certain browsers did not implement these features as "the standard" would require.
+# Other functionality.
+SeleniumTestability also provides other conveniance keywords that do not make sense to incorporate into
+SeleniumLibrary itself, mainly due to functionality not being in scope of SeleniumLibrary and Selenium
+python bindings. Do check the keyword documentation for up to date list of keywords.
+# Keyword Documentation
+Keyword documentation [here](https://marketsquare.github.io/robotframework-seleniumtestability/index.html?tag=plugin) and if you need to create one for offline usage:
+```
+python -m robot.libdoc SeleniumLibrary::plugins=SeleniumTestability
+```
+# Contributing
+[CONTRIBUTING.md](https://github.com/marketsquare/robotframework-seleniumtestability/blob/master/CONTRIBUTING.md) documents how to setup the environment for further development of SeleniumTestability.
+
+%prep
+%autosetup -n robotframework-seleniumtestability-2.1.0
+
+%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-robotframework-seleniumtestability -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 2.1.0-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..fce281b
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+e56440fccad259a7d812e83cc99e4e3b  robotframework-seleniumtestability-2.1.0.tar.gz