| Name | robotstatuschecker JSON |
| Version |
4.1.1
JSON |
| download |
| home_page | None |
| Summary | A tool for checking that Robot Framework test cases have expected statuses and log messages. |
| upload_time | 2025-02-09 14:37:02 |
| maintainer | None |
| docs_url | None |
| author | Pekka Klärck, Tatu Aalto, Robot Framework Developers |
| requires_python | <4.0,>=3.8 |
| license | 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.
|
| keywords |
robotframework
testing
testautomation
atdd
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
StatusChecker
=============
.. contents::
:local:
Introduction
------------
StatusChecker is a tool for validating that executed `Robot Framework`_
tests have expected statuses and log messages. It is mainly useful
for Robot Framework library developers who want to test their libraries
using Robot Framework.
StatusChecker project is hosted at GitHub_ and downloads are at PyPI_.
.. _Robot Framework: http://robotframework.org
.. _GitHub: https://github.com/robotframework/statuschecker
.. _PyPI: https://pypi.python.org/pypi/robotstatuschecker
.. _pip: http://pip-installer.org
Installation instructions
-------------------------
The easiest way to install StatusChecker is by using pip_::
pip install robotstatuschecker
Alternatively you can get the code by cloning the project from
GitHub_ or downloading the source distribution from PyPI_ and
extracting it. After that you can install the tool with::
python setup.py install
Usage
-----
As a tool::
python -m robotstatuschecker output.xml
python -m robotstatuschecker output.xml checked.xml
The first argument is the file to check and the latter is where to save
the results. If only one argument is given, that file is modified in place.
If you want to get log and report files, you need to generate them separately
with the ``rebot`` tool.
As a pre-Rebot modifier::
robot --prerebotmodifier robotstatuschecker.StatusChecker tests.robot
rebot --prerebotmodifier robotstatuschecker.StatusChecker output.xml
rebot --prerebotmodifier robotstatuschecker.StatusChecker --output checked.xml output.xml
When used as part of execution with ``robot``, results are checked before
log and report files are generated, but the output.xml file is not modified.
The same is true also with ``rebot`` by default, but it is possible to use
the ``--output`` option to specify where to save the modified results.
Programmatically:
.. sourcecode:: python
from robotstatuschecker import process_output
process_output('output.xml', 'checked.xml')
Also in this usage the second argument is optional and the input file is
modified in place if it is not given.
Defining expected test status
-----------------------------
By default, all tests are expected to *PASS* and have no message.
Changing the expected status to *FAIL* is done by having the word
``FAIL`` (case-sensitive) somewhere in the test documentation.
The expected error message must then follow the ``FAIL`` marker.
If the test is expected to be skipped, you can change the expected status
to *SKIP* by adding the word ``SKIP`` in the documentation. Also in
this case the expected message must follow the marker. If a test is
expected to *PASS* with a certain message, the word ``PASS`` must be
added to its documentation explicitly and the expected message given
after that.
The expected message can also be specified as a regular expression by
prefixing it with ``REGEXP:``. The specified regular expression
must match the error message fully. Having spaces between the status,
the message and the possible regular expression prefix is optional.
An alternative to using regular expressions is using glob patterns where
``*`` matches anything (including newline) and ``?`` matches any single
character. This is can be accomplished by starting the expected message
with ``GLOB:``.
Finally, it is possible to test that the message starts with something
by prefixing the expected message with ``STARTS:``.
The following examples illustrate different ways to define test
statuses and messages:
.. sourcecode:: robotframework
*** Test Cases ***
Implicit PASS
Log Hello!
Explicit PASS with message
[Documentation] PASS Expected message
Pass Execution Expected message
Expected FAIL
[Documentation] FAIL Expected failure
Fail Expected failure
Expected SKIP
[Documentation] Text before marker is ignored SKIP Expected skip
Skip Expected skip
Message using REGEXP
[Documentation] FAIL REGEXP: (IOError|OSError): .*
Fail IOError: Unknown error
Message using GLOB
[Documentation] FAIL GLOB: ??Error: *
Fail IOError: Unknown error
Message using STARTS
[Documentation] FAIL STARTS: IOError:
Fail IOError: Unknown error
Defining expected log messages
------------------------------
In addition to verifying test statuses and messages, it possible to verify
messages logged by keywords. Expected log messages are defined in the test
documentation using this syntax::
LOG x.y.z LEVEL Actual message
The syntax consists of the following parts:
- ``LOG`` marker (case-sensitive).
- Locator used for finding the message. Locators typically consists of 1-based
indices like ``2.1.3`` matching items in test and keyword body. In addition
to that, they can contain ``setup`` and ``teardown`` markers mathing test and
keyword setup and teardown.
- Optional, case-sensitive log level. If omitted, the level is ``INFO``.
Special value ``ANY`` can be used to accept any level.
- The actual log message. Possible leading and trailing whitespace is ignored.
Special value ``NONE`` (case-sensitive) can be used to indicate that there
should be no log message.
The locator can either point directly to the message to be verified or
to the parent element of the message. In the latter case the actual message
is expected to be the first item in parent's body. If the message index
is not known, it is possible use the asterisk as a wildcard like ``2.*``
to match any message. When a locator points directly to a message, it is
possible to use ``:`` as the message separator instead of ``.``, but this
support is deprecated and may be removed in the future.
If test status and message is also tested, they must be specified before
the ``LOG`` marker using the syntax explained in the previous section.
If there are multiple message to be tested, the ``LOG`` marker can be used
multiple times. In such cases it is often a good idea to split the documentation
to multiple lines.
.. sourcecode:: robotframework
*** Test cases ***
Locator points to message parent
[Documentation] LOG 1 Hello! LOG 2 first LOG 3.1 Nested!
Log Hello!
Log Many first second third
User Keyword
Locator points to directly to message
[Documentation] Splitting can enhance readability. This text is ignored.
... LOG 1.1 Hello!
... LOG 2.2 second
... LOG 3.1.1 Nested!
Log Hello!
Log Many first second third
User Keyword
Message in setup and teardown
[Documentation]
... LOG setup Hello!
... LOG teardown.1 Nested!
[Setup] Log Hello!
No Operation
[Teardown] User Keyword
Wildcard
[Documentation] LOG 1.* first
Log Many first second third
No message
[Documentation]
... LOG 1.1 one
... LOG 1.2 two
... LOG 1.3 NONE
Log Many one two
Log levels
[Documentation]
... LOG 1 DEBUG first
... LOG 2 INFO second
... LOG 3 ANY third
Log first level=DEBUG
Log second level=INFO
Log third level=DEBUG
Test status and log message
[Documentation] FAIL Expected failure
... LOG 1 INFO Hello!
... LOG 2 FAIL Expected failure
Log Hello!
Fail Expected failure
*** Keywords ***
User Keyword
Log Nested!
If the message is not known exactly, it is possible to match it as a regular
expression or glob pattern or to give just the beginning of the message.
This is accomplished by prefixing the message with ``REGEXP:``, ``GLOB:``
or ``STARTS:``, respectively, exactly like when `defining expected test status`_.
.. sourcecode:: robotframework
*** Test cases ***
Log message using REGEXP
[Documentation] LOG 1 REGEXP: Hello, .*!
Log Hello, Robots!
Log message using GLOB
[Documentation] LOG 1 GLOB: Hello, *!
Log Hello, Robots!
Log message using STARTS
[Documentation] LOG 1 STARTS: Hello
Log Hello, Robots!
Raw data
{
"_id": null,
"home_page": null,
"name": "robotstatuschecker",
"maintainer": null,
"docs_url": null,
"requires_python": "<4.0,>=3.8",
"maintainer_email": null,
"keywords": "robotframework, testing, testautomation, atdd",
"author": "Pekka Kl\u00e4rck, Tatu Aalto, Robot Framework Developers",
"author_email": null,
"download_url": "https://files.pythonhosted.org/packages/11/14/966fb211d74e4db8c07102c978da63606885fa1a68bcb7918c095f5d82fc/robotstatuschecker-4.1.1.tar.gz",
"platform": null,
"description": "StatusChecker\n=============\n\n.. contents::\n :local:\n\nIntroduction\n------------\n\nStatusChecker is a tool for validating that executed `Robot Framework`_\ntests have expected statuses and log messages. It is mainly useful\nfor Robot Framework library developers who want to test their libraries\nusing Robot Framework.\n\nStatusChecker project is hosted at GitHub_ and downloads are at PyPI_.\n\n.. _Robot Framework: http://robotframework.org\n.. _GitHub: https://github.com/robotframework/statuschecker\n.. _PyPI: https://pypi.python.org/pypi/robotstatuschecker\n.. _pip: http://pip-installer.org\n\nInstallation instructions\n-------------------------\n\nThe easiest way to install StatusChecker is by using pip_::\n\n pip install robotstatuschecker\n\nAlternatively you can get the code by cloning the project from\nGitHub_ or downloading the source distribution from PyPI_ and\nextracting it. After that you can install the tool with::\n\n python setup.py install\n\nUsage\n-----\n\nAs a tool::\n\n python -m robotstatuschecker output.xml\n python -m robotstatuschecker output.xml checked.xml\n\nThe first argument is the file to check and the latter is where to save\nthe results. If only one argument is given, that file is modified in place.\nIf you want to get log and report files, you need to generate them separately\nwith the ``rebot`` tool.\n\nAs a pre-Rebot modifier::\n\n robot --prerebotmodifier robotstatuschecker.StatusChecker tests.robot\n rebot --prerebotmodifier robotstatuschecker.StatusChecker output.xml\n rebot --prerebotmodifier robotstatuschecker.StatusChecker --output checked.xml output.xml\n\nWhen used as part of execution with ``robot``, results are checked before\nlog and report files are generated, but the output.xml file is not modified.\nThe same is true also with ``rebot`` by default, but it is possible to use\nthe ``--output`` option to specify where to save the modified results.\n\nProgrammatically:\n\n.. sourcecode:: python\n\n from robotstatuschecker import process_output\n\n process_output('output.xml', 'checked.xml')\n\nAlso in this usage the second argument is optional and the input file is\nmodified in place if it is not given.\n\nDefining expected test status\n-----------------------------\n\nBy default, all tests are expected to *PASS* and have no message.\nChanging the expected status to *FAIL* is done by having the word\n``FAIL`` (case-sensitive) somewhere in the test documentation.\nThe expected error message must then follow the ``FAIL`` marker.\n\nIf the test is expected to be skipped, you can change the expected status\nto *SKIP* by adding the word ``SKIP`` in the documentation. Also in\nthis case the expected message must follow the marker. If a test is\nexpected to *PASS* with a certain message, the word ``PASS`` must be\nadded to its documentation explicitly and the expected message given\nafter that.\n\nThe expected message can also be specified as a regular expression by\nprefixing it with ``REGEXP:``. The specified regular expression\nmust match the error message fully. Having spaces between the status,\nthe message and the possible regular expression prefix is optional.\n\nAn alternative to using regular expressions is using glob patterns where\n``*`` matches anything (including newline) and ``?`` matches any single\ncharacter. This is can be accomplished by starting the expected message\nwith ``GLOB:``.\n\nFinally, it is possible to test that the message starts with something\nby prefixing the expected message with ``STARTS:``.\n\nThe following examples illustrate different ways to define test\nstatuses and messages:\n\n.. sourcecode:: robotframework\n\n *** Test Cases ***\n Implicit PASS\n Log Hello!\n\n Explicit PASS with message\n [Documentation] PASS Expected message\n Pass Execution Expected message\n\n Expected FAIL\n [Documentation] FAIL Expected failure\n Fail Expected failure\n\n Expected SKIP\n [Documentation] Text before marker is ignored SKIP Expected skip\n Skip Expected skip\n\n Message using REGEXP\n [Documentation] FAIL REGEXP: (IOError|OSError): .*\n Fail IOError: Unknown error\n\n Message using GLOB\n [Documentation] FAIL GLOB: ??Error: *\n Fail IOError: Unknown error\n\n Message using STARTS\n [Documentation] FAIL STARTS: IOError:\n Fail IOError: Unknown error\n\n\nDefining expected log messages\n------------------------------\n\nIn addition to verifying test statuses and messages, it possible to verify\nmessages logged by keywords. Expected log messages are defined in the test\ndocumentation using this syntax::\n\n LOG x.y.z LEVEL Actual message\n\nThe syntax consists of the following parts:\n\n- ``LOG`` marker (case-sensitive).\n- Locator used for finding the message. Locators typically consists of 1-based\n indices like ``2.1.3`` matching items in test and keyword body. In addition\n to that, they can contain ``setup`` and ``teardown`` markers mathing test and\n keyword setup and teardown.\n- Optional, case-sensitive log level. If omitted, the level is ``INFO``.\n Special value ``ANY`` can be used to accept any level.\n- The actual log message. Possible leading and trailing whitespace is ignored.\n Special value ``NONE`` (case-sensitive) can be used to indicate that there\n should be no log message.\n\nThe locator can either point directly to the message to be verified or\nto the parent element of the message. In the latter case the actual message\nis expected to be the first item in parent's body. If the message index\nis not known, it is possible use the asterisk as a wildcard like ``2.*``\nto match any message. When a locator points directly to a message, it is\npossible to use ``:`` as the message separator instead of ``.``, but this\nsupport is deprecated and may be removed in the future.\n\nIf test status and message is also tested, they must be specified before\nthe ``LOG`` marker using the syntax explained in the previous section.\nIf there are multiple message to be tested, the ``LOG`` marker can be used\nmultiple times. In such cases it is often a good idea to split the documentation\nto multiple lines.\n\n.. sourcecode:: robotframework\n\n *** Test cases ***\n Locator points to message parent\n [Documentation] LOG 1 Hello! LOG 2 first LOG 3.1 Nested!\n Log Hello!\n Log Many first second third\n User Keyword\n\n Locator points to directly to message\n [Documentation] Splitting can enhance readability. This text is ignored.\n ... LOG 1.1 Hello!\n ... LOG 2.2 second\n ... LOG 3.1.1 Nested!\n Log Hello!\n Log Many first second third\n User Keyword\n\n Message in setup and teardown\n [Documentation]\n ... LOG setup Hello!\n ... LOG teardown.1 Nested!\n [Setup] Log Hello!\n No Operation\n [Teardown] User Keyword\n\n Wildcard\n [Documentation] LOG 1.* first\n Log Many first second third\n\n No message\n [Documentation]\n ... LOG 1.1 one\n ... LOG 1.2 two\n ... LOG 1.3 NONE\n Log Many one two\n\n Log levels\n [Documentation]\n ... LOG 1 DEBUG first\n ... LOG 2 INFO second\n ... LOG 3 ANY third\n Log first level=DEBUG\n Log second level=INFO\n Log third level=DEBUG\n\n Test status and log message\n [Documentation] FAIL Expected failure\n ... LOG 1 INFO Hello!\n ... LOG 2 FAIL Expected failure\n Log Hello!\n Fail Expected failure\n\n *** Keywords ***\n User Keyword\n Log Nested!\n\nIf the message is not known exactly, it is possible to match it as a regular\nexpression or glob pattern or to give just the beginning of the message.\nThis is accomplished by prefixing the message with ``REGEXP:``, ``GLOB:``\nor ``STARTS:``, respectively, exactly like when `defining expected test status`_.\n\n.. sourcecode:: robotframework\n\n *** Test cases ***\n Log message using REGEXP\n [Documentation] LOG 1 REGEXP: Hello, .*!\n Log Hello, Robots!\n\n Log message using GLOB\n [Documentation] LOG 1 GLOB: Hello, *!\n Log Hello, Robots!\n\n Log message using STARTS\n [Documentation] LOG 1 STARTS: Hello\n Log Hello, Robots!\n",
"bugtrack_url": null,
"license": "Apache License\n Version 2.0, January 2004\n http://www.apache.org/licenses/\n \n TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION\n \n 1. Definitions.\n \n \"License\" shall mean the terms and conditions for use, reproduction,\n and distribution as defined by Sections 1 through 9 of this document.\n \n \"Licensor\" shall mean the copyright owner or entity authorized by\n the copyright owner that is granting the License.\n \n \"Legal Entity\" shall mean the union of the acting entity and all\n other entities that control, are controlled by, or are under common\n control with that entity. For the purposes of this definition,\n \"control\" means (i) the power, direct or indirect, to cause the\n direction or management of such entity, whether by contract or\n otherwise, or (ii) ownership of fifty percent (50%) or more of the\n outstanding shares, or (iii) beneficial ownership of such entity.\n \n \"You\" (or \"Your\") shall mean an individual or Legal Entity\n exercising permissions granted by this License.\n \n \"Source\" form shall mean the preferred form for making modifications,\n including but not limited to software source code, documentation\n source, and configuration files.\n \n \"Object\" form shall mean any form resulting from mechanical\n transformation or translation of a Source form, including but\n not limited to compiled object code, generated documentation,\n and conversions to other media types.\n \n \"Work\" shall mean the work of authorship, whether in Source or\n Object form, made available under the License, as indicated by a\n copyright notice that is included in or attached to the work\n (an example is provided in the Appendix below).\n \n \"Derivative Works\" shall mean any work, whether in Source or Object\n form, that is based on (or derived from) the Work and for which the\n editorial revisions, annotations, elaborations, or other modifications\n represent, as a whole, an original work of authorship. For the purposes\n of this License, Derivative Works shall not include works that remain\n separable from, or merely link (or bind by name) to the interfaces of,\n the Work and Derivative Works thereof.\n \n \"Contribution\" shall mean any work of authorship, including\n the original version of the Work and any modifications or additions\n to that Work or Derivative Works thereof, that is intentionally\n submitted to Licensor for inclusion in the Work by the copyright owner\n or by an individual or Legal Entity authorized to submit on behalf of\n the copyright owner. For the purposes of this definition, \"submitted\"\n means any form of electronic, verbal, or written communication sent\n to the Licensor or its representatives, including but not limited to\n communication on electronic mailing lists, source code control systems,\n and issue tracking systems that are managed by, or on behalf of, the\n Licensor for the purpose of discussing and improving the Work, but\n excluding communication that is conspicuously marked or otherwise\n designated in writing by the copyright owner as \"Not a Contribution.\"\n \n \"Contributor\" shall mean Licensor and any individual or Legal Entity\n on behalf of whom a Contribution has been received by Licensor and\n subsequently incorporated within the Work.\n \n 2. Grant of Copyright License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n copyright license to reproduce, prepare Derivative Works of,\n publicly display, publicly perform, sublicense, and distribute the\n Work and such Derivative Works in Source or Object form.\n \n 3. Grant of Patent License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n (except as stated in this section) patent license to make, have made,\n use, offer to sell, sell, import, and otherwise transfer the Work,\n where such license applies only to those patent claims licensable\n by such Contributor that are necessarily infringed by their\n Contribution(s) alone or by combination of their Contribution(s)\n with the Work to which such Contribution(s) was submitted. If You\n institute patent litigation against any entity (including a\n cross-claim or counterclaim in a lawsuit) alleging that the Work\n or a Contribution incorporated within the Work constitutes direct\n or contributory patent infringement, then any patent licenses\n granted to You under this License for that Work shall terminate\n as of the date such litigation is filed.\n \n 4. Redistribution. You may reproduce and distribute copies of the\n Work or Derivative Works thereof in any medium, with or without\n modifications, and in Source or Object form, provided that You\n meet the following conditions:\n \n (a) You must give any other recipients of the Work or\n Derivative Works a copy of this License; and\n \n (b) You must cause any modified files to carry prominent notices\n stating that You changed the files; and\n \n (c) You must retain, in the Source form of any Derivative Works\n that You distribute, all copyright, patent, trademark, and\n attribution notices from the Source form of the Work,\n excluding those notices that do not pertain to any part of\n the Derivative Works; and\n \n (d) If the Work includes a \"NOTICE\" text file as part of its\n distribution, then any Derivative Works that You distribute must\n include a readable copy of the attribution notices contained\n within such NOTICE file, excluding those notices that do not\n pertain to any part of the Derivative Works, in at least one\n of the following places: within a NOTICE text file distributed\n as part of the Derivative Works; within the Source form or\n documentation, if provided along with the Derivative Works; or,\n within a display generated by the Derivative Works, if and\n wherever such third-party notices normally appear. The contents\n of the NOTICE file are for informational purposes only and\n do not modify the License. You may add Your own attribution\n notices within Derivative Works that You distribute, alongside\n or as an addendum to the NOTICE text from the Work, provided\n that such additional attribution notices cannot be construed\n as modifying the License.\n \n You may add Your own copyright statement to Your modifications and\n may provide additional or different license terms and conditions\n for use, reproduction, or distribution of Your modifications, or\n for any such Derivative Works as a whole, provided Your use,\n reproduction, and distribution of the Work otherwise complies with\n the conditions stated in this License.\n \n 5. Submission of Contributions. Unless You explicitly state otherwise,\n any Contribution intentionally submitted for inclusion in the Work\n by You to the Licensor shall be under the terms and conditions of\n this License, without any additional terms or conditions.\n Notwithstanding the above, nothing herein shall supersede or modify\n the terms of any separate license agreement you may have executed\n with Licensor regarding such Contributions.\n \n 6. Trademarks. This License does not grant permission to use the trade\n names, trademarks, service marks, or product names of the Licensor,\n except as required for reasonable and customary use in describing the\n origin of the Work and reproducing the content of the NOTICE file.\n \n 7. Disclaimer of Warranty. Unless required by applicable law or\n agreed to in writing, Licensor provides the Work (and each\n Contributor provides its Contributions) on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or\n implied, including, without limitation, any warranties or conditions\n of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A\n PARTICULAR PURPOSE. You are solely responsible for determining the\n appropriateness of using or redistributing the Work and assume any\n risks associated with Your exercise of permissions under this License.\n \n 8. Limitation of Liability. In no event and under no legal theory,\n whether in tort (including negligence), contract, or otherwise,\n unless required by applicable law (such as deliberate and grossly\n negligent acts) or agreed to in writing, shall any Contributor be\n liable to You for damages, including any direct, indirect, special,\n incidental, or consequential damages of any character arising as a\n result of this License or out of the use or inability to use the\n Work (including but not limited to damages for loss of goodwill,\n work stoppage, computer failure or malfunction, or any and all\n other commercial damages or losses), even if such Contributor\n has been advised of the possibility of such damages.\n \n 9. Accepting Warranty or Additional Liability. While redistributing\n the Work or Derivative Works thereof, You may choose to offer,\n and charge a fee for, acceptance of support, warranty, indemnity,\n or other liability obligations and/or rights consistent with this\n License. However, in accepting such obligations, You may act only\n on Your own behalf and on Your sole responsibility, not on behalf\n of any other Contributor, and only if You agree to indemnify,\n defend, and hold each Contributor harmless for any liability\n incurred by, or claims asserted against, such Contributor by reason\n of your accepting any such warranty or additional liability.\n \n END OF TERMS AND CONDITIONS\n \n APPENDIX: How to apply the Apache License to your work.\n \n To apply the Apache License to your work, attach the following\n boilerplate notice, with the fields enclosed by brackets \"[]\"\n replaced with your own identifying information. (Don't include\n the brackets!) The text should be enclosed in the appropriate\n comment syntax for the file format. We also recommend that a\n file or class name and description of purpose be included on the\n same \"printed page\" as the copyright notice for easier\n identification within third-party archives.\n \n Copyright [yyyy] [name of copyright owner]\n \n Licensed under the Apache License, Version 2.0 (the \"License\");\n you may not use this file except in compliance with the License.\n You may obtain a copy of the License at\n \n http://www.apache.org/licenses/LICENSE-2.0\n \n Unless required by applicable law or agreed to in writing, software\n distributed under the License is distributed on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n See the License for the specific language governing permissions and\n limitations under the License.\n ",
"summary": "A tool for checking that Robot Framework test cases have expected statuses and log messages.",
"version": "4.1.1",
"project_urls": {
"Changelog": "https://github.com/robotframework/statuschecker/tree/master/docs/releasenotes",
"Homepage": "https://github.com/robotframework/statuschecker",
"Issues": "https://github.com/robotframework/statuschecker/issues"
},
"split_keywords": [
"robotframework",
" testing",
" testautomation",
" atdd"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "fd30ece228d86aeda1c7a9cc92510860dd1e8c6f5ae68c95c9cfe60e59c6a1ca",
"md5": "41a3b32ac017675e0b8b6dd178500c51",
"sha256": "9da538486c05e99a8a03333f8d6dd7d91238700cdc3fca44fa27d31a700a721a"
},
"downloads": -1,
"filename": "robotstatuschecker-4.1.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "41a3b32ac017675e0b8b6dd178500c51",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": "<4.0,>=3.8",
"size": 16204,
"upload_time": "2025-02-09T14:37:00",
"upload_time_iso_8601": "2025-02-09T14:37:00.659533Z",
"url": "https://files.pythonhosted.org/packages/fd/30/ece228d86aeda1c7a9cc92510860dd1e8c6f5ae68c95c9cfe60e59c6a1ca/robotstatuschecker-4.1.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "1114966fb211d74e4db8c07102c978da63606885fa1a68bcb7918c095f5d82fc",
"md5": "7a1b540ac04853f7ab7756f5960e03a3",
"sha256": "5ebe9454beb6fde8aca299161a12389642b074c234deb1f860b6f699a8608e84"
},
"downloads": -1,
"filename": "robotstatuschecker-4.1.1.tar.gz",
"has_sig": false,
"md5_digest": "7a1b540ac04853f7ab7756f5960e03a3",
"packagetype": "sdist",
"python_version": "source",
"requires_python": "<4.0,>=3.8",
"size": 17072,
"upload_time": "2025-02-09T14:37:02",
"upload_time_iso_8601": "2025-02-09T14:37:02.400483Z",
"url": "https://files.pythonhosted.org/packages/11/14/966fb211d74e4db8c07102c978da63606885fa1a68bcb7918c095f5d82fc/robotstatuschecker-4.1.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-02-09 14:37:02",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "robotframework",
"github_project": "statuschecker",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "robotstatuschecker"
}
