busser-robot 0.1.3

data/vendor/robot/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/vendor/robot/MANIFEST.in

@@ -0,0 +1,4 @@
+include src/bin/*bot src/bin/*.bat
+include src/robot/htmldata/*/*.html src/robot/htmldata/*/*.js src/robot/htmldata/*/*.css
+include AUTHORS.txt BUILD.rst CONTRIBUTING.rst COPYRIGHT.txt INSTALL.rst LICENSE.txt README.rst MANIFEST.in tasks.py
+prune src/robot/htmldata/testdata

data/vendor/robot/README.rst

@@ -0,0 +1,150 @@
+Robot Framework
+===============
+
+.. contents::
+   :local:
+
+Introduction
+------------
+
+`Robot Framework <http://robotframework.org>`_ is a generic open source test
+automation framework for acceptance testing and acceptance test-driven
+development (ATDD). It has easy-to-use tabular test data syntax and it utilizes
+the keyword-driven testing approach. Its testing capabilities can be extended
+by test libraries implemented either with Python or Java, and users can create
+new higher-level keywords from existing ones using the same syntax that is used
+for creating test cases.
+
+Robot Framework is operating system and application independent. The core
+framework is implemented using `Python <http://python.org>`_, supports both
+Python 2 and Python 3, and runs also on `Jython <http://jython.org>`_ (JVM),
+`IronPython <http://ironpython.net>`_ (.NET) and `PyPy <http://pypy.org>`_.
+The framework has a rich ecosystem around it consisting of various generic
+test libraries and tools that are developed as separate projects. For more
+information about Robot Framework and the ecosystem, see
+http://robotframework.org.
+
+Robot Framework project is hosted on GitHub_ where you can find source code,
+an issue tracker, and some further documentation. See `<CONTRIBUTING.rst>`__
+if you are interested to contribute. Downloads are hosted on PyPI_, except
+for the standalone JAR distribution that is on `Maven central`_.
+
+Robot Framework development is sponsored by `Robot Framework Foundation
+<http://robotframework.org/foundation>`_.
+
+.. _GitHub: https://github.com/robotframework/robotframework
+.. _PyPI: https://pypi.python.org/pypi/robotframework
+.. _Maven central: http://search.maven.org/#search%7Cga%7C1%7Ca%3Arobotframework
+
+.. image:: https://img.shields.io/pypi/v/robotframework.svg?label=version
+   :target: https://pypi.python.org/pypi/robotframework
+   :alt: Latest version
+
+.. image:: https://img.shields.io/pypi/l/robotframework.svg
+   :target: http://www.apache.org/licenses/LICENSE-2.0.html
+   :alt: License
+
+.. image:: https://robotframework-slack.herokuapp.com/badge.svg
+   :target: https://robotframework-slack.herokuapp.com
+   :alt: Slack channel
+
+Installation
+------------
+
+If you already have Python_ with `pip <http://pip-installer.org>`_ installed,
+you can simply run::
+
+    pip install robotframework
+
+Alternatively you can get Robot Framework source code by downloading the source
+distribution from PyPI_ and extracting it, or by cloning the project repository
+from GitHub_. After that you can install the framework with::
+
+    python setup.py install
+
+For more detailed installation instructions, including installing Python,
+Jython, IronPython and PyPy, see `<INSTALL.rst>`__.
+
+Example
+-------
+
+Below is a simple example test case for testing login to some system.
+You can find more examples with links to related demo projects from
+http://robotframework.org.
+
+.. code:: robotframework
+
+    *** Settings ***
+    Documentation     A test suite with a single test for valid login.
+    ...
+    ...               This test has a workflow that is created using keywords in
+    ...               the imported resource file.
+    Resource          resource.robot
+
+    *** Test Cases ***
+    Valid Login
+        Open Browser To Login Page
+        Input Username    demo
+        Input Password    mode
+        Submit Credentials
+        Welcome Page Should Be Open
+        [Teardown]    Close Browser
+
+Usage
+-----
+
+Starting from Robot Framework 3.0, tests are executed from the command line
+using the ``robot`` script or by executing the ``robot`` module directly
+like ``python -m robot`` or ``jython -m robot``. Older Robot Framework
+versions have Python interpreter specific ``pybot``, ``jybot`` and ``ipybot``
+scripts that still work but will be deprecated and removed in the future.
+
+The basic usage is giving a path to a test case file or directory as an
+argument with possible command line options before the path::
+
+    robot tests.robot
+    robot --variable HOST:example.com --outputdir results path/to/tests/
+
+Additionally there is ``rebot`` tool for combining results and otherwise
+post-processing outputs::
+
+    rebot --name Example output1.xml output2.xml
+
+Run ``robot --help`` and ``rebot --help`` for more information about the command
+line usage. For a complete reference manual see `Robot Framework User Guide`_.
+
+Documentation
+-------------
+
+- `Robot Framework User Guide
+  <http://robotframework.org/robotframework/#user-guide>`_
+- `Standard libraries
+  <http://robotframework.org/robotframework/#standard-libraries>`_
+- `Built-in tools
+  <http://robotframework.org/robotframework/#built-in-tools>`_
+- `API documentation
+  <http://robot-framework.readthedocs.org>`_
+- `General documentation and demos
+  <http://robotframework.org/#documentation>`_
+
+Support and contact
+-------------------
+
+- `robotframework-users
+  <https://groups.google.com/group/robotframework-users/>`_ mailing list
+- `Slack <https://robotframework-slack.herokuapp.com>`_ community
+- `#robotframework <http://webchat.freenode.net/?channels=robotframework&prompt=1>`_
+  IRC channel on freenode
+- `@robotframework <https://twitter.com/robotframework>`_ on Twitter
+- `Other forums <http://robotframework.org/#support>`_
+
+License
+-------
+
+Robot Framework is open source software provided under the `Apache License
+2.0`__. Robot Framework documentation and other similar content use the
+`Creative Commons Attribution 3.0 Unported`__ license. Most libraries and tools
+in the ecosystem are also open source, but they may use different licenses.
+
+__ http://apache.org/licenses/LICENSE-2.0
+__ http://creativecommons.org/licenses/by/3.0

data/vendor/robot/atest/README.rst

@@ -0,0 +1,235 @@
+Robot Framework acceptance tests
+================================
+
+Acceptance tests for Robot Framework are naturally created using Robot
+Framework itself. This folder contains all those acceptance tests and other
+test data they need.
+
+.. contents::
+   :local:
+
+Directory contents
+------------------
+
+run.py
+    A script for running acceptance tests. See `Running acceptance tests`_
+    for further instructions.
+
+genrunner.py
+    Script to generate acceptance test runners based on test data files.
+
+    Usage:  ``atest/genrunner.py atest/testdata/path/data.robot [atest/robot/path/runner.robot]``
+
+robot/
+    Contains actual acceptance test cases. See `Test data`_ section for details.
+
+resources/
+    Resources needed by acceptance tests in the ``robot`` folder.
+
+testdata/
+    Contains test cases that are run by actual acceptance tests in the
+    ``robot`` folder. See `Test data`_ section for details.
+
+testresources/
+    Contains resources needed by test cases in the ``testdata`` folder.
+    Some of these resources are also used by `unit tests <../utest/README.rst>`_.
+
+results/
+    The place for test execution results. This directory is generated when
+    acceptance tests are executed. It is in ``.gitignore`` and can be safely
+    deleted any time.
+
+Running acceptance tests
+------------------------
+
+Robot Framework's acceptance tests are executed using the `<run.py>`__
+script. It has two mandatory arguments, the Python interpreter to use
+when running tests and path to tests to be executed, and it accepts also
+all same options as Robot Framework. The script itself should always be
+executed with Python. Run it with ``--help`` or see documentation in its
+`source code <run.py>`__ for more information.
+
+To run all the acceptance tests, execute the ``atest/robot`` folder
+entirely using the selected interpreter::
+
+    atest/run.py python atest/robot
+    atest/run.py jython atest/robot
+
+The commands above will execute all tests, but you typically want to skip
+`Telnet tests`_ and tests requiring manual interaction. These tests are marked
+with the ``no-ci`` tag and can be easily excluded::
+
+    atest/run.py python --exclude no-ci atest/robot
+
+A sub test suite can be executed simply by running the folder or file
+containing it. On modern machines running all acceptance tests ought to
+take less than ten minutes with Python, but with Jython the execution time
+is considerably longer. This is due to Jython being somewhat slower than
+Python in general, but the main reason is that the JVM is started by
+acceptance dozens of times and that always takes few seconds.
+
+Before a release tests should be executed separately using  Python, Jython,
+IronPython and PyPy to verify interoperability with all supported interpreters.
+Tests should also be run using different interpreter versions (when applicable)
+and on different operating systems.
+
+The results of the test execution are written into an interpreter specific
+directory under the ``atest/results`` directory. Temporary outputs created
+during the execution are created under the system temporary directory.
+
+Test data
+---------
+
+The test data is divided to two, test data part (``atest/testdata`` folder) and
+running part (``atest/robot`` folder). Test data side contains test cases for
+different features. Running side contains the actual acceptance test cases
+that run the test cases on the test data side and verify their results.
+
+The basic mechanism to verify that a test case in the test data side is
+executed as expected is setting the expected status and possible error
+message in its documentation. By default tests are expected to pass, but
+having ``FAIL`` (this and subsequent markers are case sensitive) in the
+documentation changes the expectation. The text after the ``FAIL`` marker
+is the expected error message, which, by default, must match the actual
+error exactly. If the error message starts with ``REGEXP:``, ``GLOB:`` or
+``STARTS:``, the expected error is considered to be a regexp or glob pattern
+matching the actual error, or to contain the beginning of the error. All
+other details can be tested also, but that logic is in the running side.
+
+Test tags
+---------
+
+The tests on the running side (``atest/robot``) contains tags that are used
+to include or exclude them based on the platform and required dependencies.
+Selecting tests based on the platform is done automatically by the `<run.py>`__
+script, but additional selection can be done by the user to avoid running
+tests with `precondtions`_ that are not met.
+
+manual
+  Require manual interaction from user. Used with Dialogs library tests.
+
+telnet
+  Require a telnet server with test account running at localhost. See
+  `Telnet tests`_ for details.
+
+no-ci
+  Tests which are not executed at continuous integration. Contains all tests
+  tagged with ``manual`` or ``telnet``.
+
+require-yaml, require-docutils, require-pygments, require-lxml, require-screenshot, require-tools.jar
+  Require specified Python module or some other external tool to be installed.
+  See `Preconditions`_ for details and exclude like ``--exclude require-lxml``
+  if needed.
+
+require-windows, require-jython, ...
+  Tests that require certain operating system or Python interpreter.
+  Excluded automatically outside these platforms.
+
+no-windows, no-osx, no-jython, no-ipy,  ...
+  Tests to be excluded on certain operating systems or Python interpreters.
+  Excluded automatically on these platforms.
+
+Examples:
+
+.. code:: bash
+
+    # Exclude tests requiring manual interaction or running telnet server.
+    atest/run.py python --exclude no-ci atest/robot
+
+    # Same as the above but also exclude tests requiring docutils and lxml
+    atest/run.py python -e no-ci -e require-docutils -e require-lxml atest/robot
+
+    # Run only tests related to Java integration. This is considerably faster
+    # than running all tests on Jython.
+    atest/run.py jython --include require-jython atest/robot
+
+Preconditions
+-------------
+
+Certain Robot Framework features require optional external modules or tools
+to be installed, and naturally tests related to these features require same
+modules/tools as well. This section lists what preconditions are needed to
+run all tests successfully. See `Test tags`_ for instructions how to avoid
+running certain tests if all preconditions are not met.
+
+Required Python modules
+~~~~~~~~~~~~~~~~~~~~~~~
+
+These Python modules need to be installed:
+
+- `docutils <http://docutils.sourceforge.net/>`_ is needed with tests related
+  to parsing test data in reStructuredText format and with Libdoc tests
+  for documentation in reST format.
+- `Pygments <http://pygments.org/>`_ is needed by Libdoc tests for syntax
+  highlighting.
+- `PyYAML <http://pyyaml.org/>`__ is required with tests related to YAML
+  variable files.
+- `lxml <http://lxml.de/>`__ is needed with XML library tests. Not compatible
+  with Jython or IronPython.
+
+It is possible to install the above modules using ``pip`` either
+individually or by using the provided `<requirements.txt>`__ file:
+
+.. code:: bash
+
+    # Install individually
+    pip install 'docutils>=0.9'
+    pip install pygments
+    pip install pyyaml
+    pip install lxml
+
+    # Install using requirements.txt
+    pip install -r atest/requirements.txt
+
+Notice that the lxml module may require compilation on Linux, which in turn
+may require installing development headers of lxml dependencies. Alternatively
+lxml can be installed using a system package manager like
+``sudo apt-get install python-lxml``.
+
+Because lxml is not compatible with Jython or IronPython, tests requiring it
+are excluded automatically when using these interpreters.
+
+Screenshot module or tool
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Screenshot library tests require a platform dependent module or tool that can
+take screenshots. See `Screenshot library documentation`__ for details.
+
+__ http://robotframework.org/robotframework/latest/libraries/Screenshot.html
+
+``tools.jar``
+~~~~~~~~~~~~~
+
+Libdoc requires ``tools.jar``, which is part of the standard JDK installation,
+to be in ``CLASSPATH`` when reading library documentation from Java source
+files. In addition to setting ``CLASSPATH`` explicitly, it is possible to
+put ``tools.jar`` into the ``ext-lib`` directory in the project root and
+``CLASSPATH`` is set automatically.
+
+Telnet tests
+------------
+
+Running telnet tests requires some extra setup. Instructions how to run them
+can be found from `<testdata/standard_libraries/telnet/README.rst>`_.
+If you don't want to run an unprotected telnet server on your machine, you can
+always skip these tests by excluding tests with a tag ``telnet`` or ``no-ci``.
+
+License and copyright
+---------------------
+
+All content in the ``atest`` folder is under the following copyright::
+
+    Copyright 2008-2015 Nokia Networks
+    Copyright 2016-     Robot Framework Foundation
+
+    Licensed under the Apache License, Version 2.0 (the "License");
+    you may not use this file except in compliance with the License.
+    You may obtain a copy of the License at
+
+        http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.