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

I struck in one problem in which I want to store Value returned from 1st keyword in variable during initial run and then using that variable in another keywords without running the 1st keyword again .

I tried below code but not able to resolve the issue.

Create Account Post Request
    ${response}=    call post request    ${headers2}    ${base_url}   ${base_url_account}    ${account_data}
    log    ${response}
    Should Be True     ${response.status_code} == 201
    ${account_id}    get value from json     ${response.json()}    id
    log    ${account_id}
    RETURN    ${account_id}

Get Network ID    --> [While running this keyword Create Account Post Request will run again which updates the account ID which I don't want]
    ${acc}=   Create Account Post Request  --> [During this It will run Create Account Post Request again which I don't want]
    log    ${acc}

My questions are :

1. How to use account_ID in any keywords without running the first keyword again and again ?
2. How to use return value from 1st keyword in any other keywords? [Condition, I don't want to run 1st keyword again to get the return value]

Below scenario is expected :

1. 1st Keyword ran
2. 1st Keyword return some value
3. Store value in some variable
4. Use returned value anywhere in the suite file, in any keyword within the suite, in any test case .

When using Given/When/Then/etc to match keywords that start with a variable ${...}, then Give/When/Then is captured into the variable value.

According to Ignoring Given/When/Then/And/But prefixes,

Prefixes Given, When, Then, And and But are dropped when matching keywords are searched, if no match with the full name is found

Is there a builtin method to reverse this logic such that it checks for the prefix-dropped version first?

*** Keywords ***
${url} is open
    Log To Console           Open "${url}"

${ele} is clicked
    Log To Console           Click "${ele}"

${ele} should be visible
    Log To Console           Is Visible "${ele}"


*** Variables ***
${url}          https://google.com
${btn_1}        xpath=//a/b/c
${modal_2}      xpath=//a/b/c


*** Test Cases ***
Valid Login
    Given ${url} is open
    When ${btn_1} is clicked
    Then ${modal_2} should be visible

Outputs

Open "Given https://google.com"
Click "When xpath=//a/b/c"
Is Visible "Then xpath=//a/b/c"

Wanted output

Open "https://google.com"
Click "xpath=//a/b/c"
Is Visible "xpath=//a/b/c"

I can get this behaviour by changing https://github.com/robotframework/robotframework/blob/master/src/robot/running/namespace.py#L292-L298 to

        runner = self._get_runner_from_suite_file(name)
        if not runner and '.' in name:
            runner = self._get_explicit_runner(name)
        if not runner:
            runner = self._get_bdd_style_runner(name)
        if not runner:
            runner = self._get_implicit_runner(name)

As discussed in issue #4562, if no condition is set on the WHILE loop, the condition should be True by default.

Here is an example :

*** Test Cases ***
Optional WHILE loop condition
    WHILE
        Log     Test
    END

Currently, the error raised when the limit of the WHILE loop is reached isn't customizable. As a result of the issue #4562, we decided to add an option named on_limit_message on the WHILE loop.

Here is an example :

*** Test Cases ***
On limit message
    WHILE    True    limit=5    on_limit_message=Custom error message
        Log     Test
    END

If a listener runs a keyword in the end_suite handler, in the context of that keyword, the in_teardown is false.

test.robot

*** Settings ***
Library           ContextAccess.py
Suite Teardown    Run Keywords    In Teardown Should Be True

*** Test Cases ***
Placeholder
    No Operation

Listener.py

from robot.libraries.BuiltIn import BuiltIn

ROBOT_LISTENER_API_VERSION = 2


def end_suite(name, attributes):
    BuiltIn().run_keyword('In Teardown Should Be True')

ContextAccess.py

from robot.running.context import EXECUTION_CONTEXTS
from robot.libraries.BuiltIn import BuiltIn


def in_teardown_should_be_true():
    BuiltIn().run_keyword('Should Be True',
                          EXECUTION_CONTEXTS.current.in_teardown)

Running robot --listener Listener.py .\test.robot results in a failure:

Recently, I am running a project with pabot, and I found that sometimes the app stocked. And I attach and see the stack, found that the timer was killed before it work out. So that the robot app cannot stop. Specfically, the code is here.

I think we might need to consider this condition in the sleep(0) loop to avoid this.