There have been several requests to be able to mark tests skipped: #812, #837, #964, #1732, #2064. Some of them use different term than skip (e.g. warn or blacklist) but the basic idea is similar.

So far all such requests have been rejected because Robot Framework already has a concept of non-critical tests and non-critical failures with a clear error message can be used to emulate skipping. I'm not inherently against skipping, though, and see that explicit SKIP status would often be more clear than non-critical FAIL. Many other test tool also has such status and being compatible with them would be nice.

I'm not planning to implement this functionality in the foreseeable future, but I wanted to open an issue about it to have a place where to discuss it. The main problem with implementation is that it would be quite a big task. The first step would be designing how the functionality actually should work. At least these things should be taken into account:

1. How to mark a test skipped. Possibilities include:
   • Based on tags from the command line.
   • Using a BuiltIn keyowrd.
   • Using a custom exception in a test library.
2. How skipped tests affect statistics?
3. How skipped tests affect overall execution result? What should the report background be if there are passed and skipped tests in a suite? What if there are only skipped?

I encourage people interested about the skip status to comment here or possibly start a discussion on the robotframework-users mailing list or on the new Slack community. If we can agree with the overall design, someone can then start actually implementing the functionality.

This is the equivalent of PR #1776 but for variables instead of keywords.

I've moved some of the reusable recommendation code from namespace.py to utils/match.py in a new FuzzyMatcher class. Trying to balance code duplication and complexity in this refactoring was tricky, so criticism/ideas are welcome.

There are a lot of special cases for variable naming, including accessing variable indexes, accessing extended variables, and accessing nested variables. I have only partially handled these special cases - recommendations for misspellings of the base variable name will generally work, but anything more complex will not work, and the recommendations will not include the index or extended variable syntax.

I reworded some of the missing variable error messages, just to make them subjectively sound better. For example, Non-existing variable '%s' is now Variable '%s' not found. This breaks many tests throughout atest, but in this PR I have not fixed those tests yet. I'll fix them if this rewording/rephrasing is approved.

For example recommendations, please see the new test cases I've added.

My tests starts to fall down. Everything worked fine until I update my Windows 10 two days ago. I downgrade windows but this doesn't help. I also tried to upgrade robot framework and selenium2library and this doesn't helped. This bug occurs for every browser I used (chrome, ff and edge).

[ ERROR ] Unexpected error: IOError: [Errno 0] Error Traceback (most recent call last): File "c:\python27\lib\site-packages\robot\utils\application.py", line 83, in _execute rc = self.main(arguments, **options) File "c:\python27\lib\site-packages\robot\run.py", line 445, in main result = suite.run(settings) File "c:\python27\lib\site-packages\robot\running\model.py", line 248, in run self.visit(runner) File "c:\python27\lib\site-packages\robot\model\testsuite.py", line 161, in visit visitor.visit_suite(self) File "c:\python27\lib\site-packages\robot\model\visitor.py", line 86, in visit_suite suite.suites.visit(self) File "c:\python27\lib\site-packages\robot\model\itemlist.py", line 76, in visit item.visit(visitor) File "c:\python27\lib\site-packages\robot\model\testsuite.py", line 161, in visit visitor.visit_suite(self) File "c:\python27\lib\site-packages\robot\model\visitor.py", line 87, in visit_suite suite.tests.visit(self) File "c:\python27\lib\site-packages\robot\model\itemlist.py", line 76, in visit item.visit(visitor) File "c:\python27\lib\site-packages\robot\model\testcase.py", line 74, in visit visitor.visit_test(self) File "c:\python27\lib\site-packages\robot\running\runner.py", line 159, in visit_test self._output.end_test(ModelCombiner(test, result)) File "c:\python27\lib\site-packages\robot\output\output.py", line 59, in end_test LOGGER.end_test(test) File "c:\python27\lib\site-packages\robot\output\logger.py", line 183, in end_test logger.end_test(test) File "c:\python27\lib\site-packages\robot\output\console\verbose.py", line 51, in end_test self._writer.status(test.status, clear=True) File "c:\python27\lib\site-packages\robot\output\console\verbose.py", line 114, in status self._clear_status() File "c:\python27\lib\site-packages\robot\output\console\verbose.py", line 124, in _clear_status self._write_info() File "c:\python27\lib\site-packages\robot\output\console\verbose.py", line 90, in _write_info self._stdout.write(self._last_info) File "c:\python27\lib\site-packages\robot\output\console\highlighting.py", line 51, in write self.stream.write(console_encode(text, stream=self.stream))

Originally submitted to Google Code by tookko on 15 Oct 2009

Similar to "Convert to Integer", "Convert to Date / Datetime" (e.g. using strptime() for strings) would be useful when you need to do date comparison.

JavadocTool, Messager and ModifierFilter is moved to a different package since Jigsaw.

Checked with

• openjdk version "10.0.1" 2018-04-17 OpenJDK Runtime Environment (build 10.0.1+10-Ubuntu-3ubuntu1)
• java version "9.0.4" Java(TM) SE Runtime Environment (build 9.0.4+11)
• java version "1.8.0_171" Java(TM) SE Runtime Environment (build 9.0.4+11)

Originally submitted to Google Code by bryan.oakley on 27 Aug 2012

I would like to see a listener mode that passes the actual objects to the listeners rather than just a few attributes. For example, I would like to be able to write a listener like this:

ROBOT_LISTENER_API_VERSION = 3
def start_suite(suite):
    print "starting suite", suite.name

Likewise for test cases and keywords.

Implementation is pretty straight-forward. In robot/output/listeners.py a new clause would be added for each method. For example:

def start_suite(self, suite):
    for li in self._listeners:
        if li.version == 1:
            li.call_method(li.start_suite, suite.name, suite.doc)
        elif li.version == 2:
            attrs = self._get_start_attrs(suite, 'metadata')
            attrs.update({'tests' : [t.name for t in suite.tests],
                          'suites': [s.name for s in suite.suites],
                          'totaltests': suite.get_test_count()})
            li.call_method(li.start_suite, suite.name, attrs)
        elif li.version == 3: 
            li.call_method(li.start_suite, suite)

This takes a big step forward toward being able to control a test run via the listener interface. The next step would be to put methods on the objects that control the state of the test run. For example, a start_suite listener might do something like 'suite.fail("blah blah")' to cause the suite to fail at the point the listener was called.

The modification of the objects is not the subject of this feature request; that will come in a later feature request. This request is solely for the ability for the listener interface to pass the objects to the listeners.

UPDATE: Jump to this comment to skip old discussion and to see how this new API is actually going to be implemented.

Originally submitted to Google Code by tookko on 19 Nov 2009

Complicated user keywords in resource files are typically built by breaking the desired functionality into smaller, lower level user keywords which are then used by the higher level user keyword. For maintainability purposes it's often desirable that the lower level keywords are not used directly from test cases, but only the higher level ones.

While this can be tackled softly by usage of documentation tags, it would be useful to have a [Private] modifier for keywords, which would make it not possible to use the keyword from outside the same resource file.

*** Test Cases ***
Example
    do thing    09/15/2021

maybe something like

@deco.keyword(converters={date: parse_date})
def do_thing(value: date):
    ...

def parse_date(value: str) -> date:
    ...

Originally submitted to Google Code by Andreas.EbbertKarroum on 30 Mar 2010

When issue 500 is implemented, it would be nice to supply with the [Template] keyword not only the test case that should be used, but also, in what language that template is written.

When I say

[Template] User Login en

RF will ignode prefixes "Given", "When", "Then", and "And" from keywords. When I specify another language, like "de", then "Gegeben", "Wenn", "Dann", and "Und".

This has already been briefly discussed in the user group: http://groups.google.com/group/robotframework-users/browse_thread/thread/488c5bc04ab2315d/7f81d5b118e7aa7a?lnk=gst&q=german#7f81d5b118e7aa7a

Please add support for creating JUnit xml output report, we need this badly. Since most other tool support that. Like right now we have pybot -x for generating xUnit xml format report files. Similarly plz add support to generate JUnit xml format report file.

Or maybe point me to some script which will convert robot output.xml to JUnit format (http://llg.cubic.org/docs/junit/)

Originally submitted to Google Code by datakurre on 29 Jul 2013

There's an on-going GSOC (2013) project for enhancing the current ReST-parser to support plain text test syntax (in addition to the current table syntax, which is based on HTML parser).

https://www.google-melange.com/gsoc/project/google/gsoc2013/vivekkodu/16001

The GSOC project is coordinated by Plone Foundation, because there has been a lot of interest in Plone community for embedding Robot Framework tests into ReST-based documentation similarly to Python doctests. The work for the GSOC project is done by Vivek Kumar Verma (https://github.com/vivekkodu/). I'm mentoring the project.

My hope is that someone from the core team could review the current work and file GitHub issues because the GitHub repo exists solely for this feature) for raised issues that should fixed to make the mergeable for Robot Framework core:

https://github.com/datakurre/robotframework/compare/GSOC2013

or

https://github.com/datakurre/robotframework/compare/GSOC2013.patch

The design decisions for this feature have been discussed earlier at: https://groups.google.com/forum/#!topic/robotframework-devel/XrnrkSUq0KI

The HTML of the RF documentation is such one can only open a doc on the same page. Most of the time I need to open a number of them so have to open multiple pages. The current design breaks a very common use pattern of allowing the user to choose how to open a link.

http://robotframework.org/robotframework/

Hi,

I am aware that the Log To Console keyword appends a new line after the message is printed, but that means that every first logged message will end up being printed in the same line of whatever was printed before during the execution of the test suite (e.g. the test case name). I think that the new line should be added before, and not after.

Introduction

With nested keyword structures, especially with recursive keyword calls and with WHILE and FOR loops, the log file can get hard do understand with many different nesting levels. Such nested structures also increase output.xml size, because even a simple keyword like

*** Keywords ***
Keyword
    Log    Robot
    Log    Framework

creates this much content:

<kw name="Keyword">
<kw name="Log" library="BuiltIn">
<arg>Robot</arg>
<doc>Logs the given message with the given level.</doc>
<msg timestamp="20230103 20:06:36.663" level="INFO">Robot</msg>
<status status="PASS" starttime="20230103 20:06:36.663" endtime="20230103 20:06:36.663"/>
</kw>
<kw name="Log" library="BuiltIn">
<arg>Framework</arg>
<doc>Logs the given message with the given level.</doc>
<msg timestamp="20230103 20:06:36.663" level="INFO">Framework</msg>
<status status="PASS" starttime="20230103 20:06:36.663" endtime="20230103 20:06:36.664"/>
</kw>
<status status="PASS" starttime="20230103 20:06:36.663" endtime="20230103 20:06:36.664"/>
</kw>

We have had --flattenkeywords option for "flattening" such structures since RF 2.8.2 (#1551) and it works great. When a keyword is flattened, its child keywords and control structures are removed otherwise, but all their messages are preserved. It doesn't affect output.xml generated during execution, but flattening happens when output.xml files are parsed and can save huge amounts of memory. When --flattenkeywords is used with Rebot, it is possible to create a new flattened output.xml. For example, the above structure is converted into this if Keyowrd is flattened:

<kw name="Keyword">
<doc>_*Content flattened.*_</doc>
<msg timestamp="20230103 20:06:36.663" level="INFO">Robot</msg>
<msg timestamp="20230103 20:06:36.663" level="INFO">Framework</msg>
<status status="PASS" starttime="20230103 20:06:36.663" endtime="20230103 20:06:36.664"/>
</kw>

Proposal

Flattening works based on keyword names and based on tags, but it needs to be activated separately from the command line. This issue proposes adding new built-in tag robot:flatten that activates this behavior automatically. Removing top level keywords from tests and leaving only their messages doesn't make sense, so robot:flatten should be usable only as a keyword tag.

This functionality should work already during execution so that flattened keywords and control structures are never written to output.xml file. This avoid output.xml file growing big and is likely to also enhance the performance a bit.

Open questions

There are some open questions related to the design still:

• [ ] Should start/end_keyword listener methods be called with flattened keywords? I believe not, but I don't feel too strongly about this.
• [ ] Should we add Content flattened to keyword documentation like we do with --flattenkeywords? I believe not. There's the robot:flatten tag to indicate that anyway.
• [ ] Should --flattenkeywords be changed to work during execution as well? I believe yes, but that requires a separate issue.
• [ ] Should automatic TRACE level logging of arguments and return values of flattened keywords be disabled? I believe yes, but this isn't high priority.

Possible future enhancements

--flattenkeywords allows flattening WHILE or FOR loops or all loop iterations. Something like that would be convenient with built-in tags as well. We could consider something like robot:flatten:while and robot:flatten:iteration to support that, but I believe that's something that can wait until future versions.

Another alternative would be allowing tags with control structures as shown in the example below. This would require parser and model changes but could also have other use cases. That's certainly out of the scope of RF 6.1, though.

*** Keywords ***
Keyword
    WHILE    True
        [Tags]    robot:flatten
        Nested
    END

Suite names are got from file or directory names by default so that, for example, example_suite.robot creates a suite Example Suite. This works fine in general, but makes it inconvenient or even impossible to use special characters like ! or _. Longer suite names can also be inconvenient as file/directory names. An easy solution to allow using whatever names is adding a new Name. The name would still be set based on the file/directory name by default, but this new setting would allow overriding it.

Being able to set a custom name for suites like this would make issue #4015 more powerful. Without this you needed to use the --name option in addition to __init__.robot files to be able to fully configure the virtual top level suite created when executing multiple files/directories.

This change only affects parsing and is fairly straightforward. This is a good issue for anyone interested to get more familiar with Robot's parser!

1 Test3.py init use run keyword to invoke an external KW

#!/usr/bin/python3
from robot.libraries.BuiltIn import BuiltIn

class Test3:
    def __init__(self):
        self.name = "Test3"
        self.builtin = BuiltIn()
        self.builtin.run_keyword("Print Log", self.name)
    def test_kw(self):
        return self.name

2 Test Case

*** Settings ***
Library     ../lib/Test3.py

*** Test Cases ***
001 Run Keyword In Lib Init Issue
    [Tags]    Priority
    ${res}=    Test3.test_kw
    Should Be Equal    ${res}    Test3

*** Keywords ***
Print Log
    [Arguments]    ${msg}
    Log To Console    \n****------****\n\n${msg}\n

When execute this robot file, case would pass but reporting errors while generating reports

C:\Users\ellgjjg\Documents\work\git\trainning\training\robot\issue>robot 1__init_run_keyword.robot

****------****

Test3

==============================================================================
Init Run Keyword :: Variable priorities.
==============================================================================  
001 Run Keyword In Lib Init Issue
****------****

Test3

001 Run Keyword In Lib Init Issue                                     | PASS |  
------------------------------------------------------------------------------  
Init Run Keyword :: Variable priorities.                              | PASS |  
1 test, 1 passed, 0 failed
==============================================================================  
Output:  C:\Users\ellgjjg\Documents\work\git\trainning\training\robot\issue\output.xml
[ ERROR ] Reading XML source 'C:\Users\ellgjjg\Documents\work\git\trainning\training\robot\issue\output.xml' failed: Incompatible child element 'kw' for 'robot'.

Try --help for usage information.

C:\Users\ellgjjg\Documents\work\git\trainning\training\robot\issue>

output.zip

I think there some issue to parse the output.xml,More importantly, the KW "Print Log" is executed twice, please help to look on this issue, We have some requirements that call external KW when lib is initialized. Thanks!