|
| 1 | +======================== |
| 2 | +robotstatuschecker 2.1.0 |
| 3 | +======================== |
| 4 | + |
| 5 | + |
| 6 | +.. default-role:: code |
| 7 | + |
| 8 | + |
| 9 | +StatusChecker is a tool for validating that executed `Robot Framework`_ test cases |
| 10 | +have expected statuses and log messages. It is mainly useful for Robot Framework |
| 11 | +test library developers who want to use Robot Framework to also test their libraries. |
| 12 | +StatusChecker 1.4 and newer are compatible with Python 3.6+. |
| 13 | + |
| 14 | +StatusChecker project is hosted at GitHub and downloads are at PyPI_ |
| 15 | +.. _Robot Framework: http://robotframework.org |
| 16 | +.. _PyPI: https://github.com/robotframework/statuschecker |
| 17 | +.. _issue tracker: https://github.com/robotframework/SeleniumLibrary/issues?q=milestone%3Av2.1.0 |
| 18 | + |
| 19 | + |
| 20 | +.. contents:: |
| 21 | + :depth: 2 |
| 22 | + :local: |
| 23 | + |
| 24 | +Most important enhancements |
| 25 | +=========================== |
| 26 | + |
| 27 | +Wildcard support for the log verification (`#32`_) |
| 28 | +-------------------------------------------------- |
| 29 | +Now it possible to verify keyword log messages with a wildcard (*), example with 1:*. |
| 30 | +This allows to verify that log massage is somewhere in the keyword, but specific index |
| 31 | +of the log message is not mandatory anymore. |
| 32 | +
|
| 33 | +Full list of fixes and enhancements |
| 34 | +=================================== |
| 35 | + |
| 36 | +.. list-table:: |
| 37 | + :header-rows: 1 |
| 38 | + |
| 39 | + * - ID |
| 40 | + - Type |
| 41 | + - Priority |
| 42 | + - Summary |
| 43 | + * - `#32`_ |
| 44 | + - enhancement |
| 45 | + - high |
| 46 | + - Wildcard support for the log verification |
| 47 | + |
| 48 | +Altogether 1 issue. View on the `issue tracker <https://github.com/robotframework/statuschecker/issues?q=milestone%3Av2.1.0>`__. |
| 49 | + |
| 50 | +.. _#32: https://github.com/robotframework/statuschecker/issues/32 |
0 commit comments