StatusChecker 3.0.1

When test looks like this:

Test
    [Documentation]    LOG 1:1    KALA
    Log KALA

prior RF 6.1 doc was returned like: LOG 1:1 KALA, with single pace between 1.1 and KALA. But in RF 6.1 doc is returned as is. This causes problem in validation message and being backwards compatible.

StatusChecker 3.0.0

StatusChecker is a tool for validating that executed Robot Framework test cases have expected statuses and log messages. It is mainly useful for Robot Framework test library developers who want to use Robot Framework to also test their libraries. StatusChecker 3 supports Python 3 and RF 5 and 6.

StatusChecker 2.1.0

StatusChecker is a tool for validating that executed Robot Framework test cases have expected statuses and log messages. It is mainly useful for Robot Framework test library developers who want to use Robot Framework to also test their libraries. StatusChecker 1.4 and newer are compatible with Python 3.6+.

Now it possible to verify keyword log messages with a wildcard (), example with 1:. This allows to verify that log massage is somewhere in the keyword, but specific index of the log message is not mandatory anymore.

StatusChecker 2.0.3

Fixes regression in 2.0.2

More details in release notes

StatusChecker 2.0.2

Fixes bug accessing keywords in teardown without TEARDOWN marker.

More details in release notes

StatusChecker 2.0.1

Fixes regression introduced in release 2.0.0 and Rf 3.2.2.

For more details see release notes

StatusChecker 2.0

Support for Robot Framework 4.0 and allows to define suite setup and teardown by own prefix. Also drops Python 2 support.

StatusChecker 1.5

Fixes deprecation warning with Robot Framework 4.0

StatusChecker 1.4

Add support for validating logger.error logging.

StatusChecker 1.3

Added Python 3 support.