Using a timeouted keyword with wrong number of arguments causes `FrameworkError`

[GoogleCodeExporter]

The executed keyword will fail normally, but the possible keywords
afterwards will fail with FrameworkError. The simplest example
demonstrating this is below.

*** Test Cases ***
Test
    KW  wrong args
    [Teardown]  No Operation

*** Keywords ***
KW  [Timeout]  1 seconds
    No Operation

It's possible to get the test fail outside teardown using `Run Keyword And
Ignore/Expect Error`. In these cases the original syntax error is also
hidden which makes debugging the problem harder. This kind of errors
shouldn't actually be hidden, but that's another issue.

Original issue reported on code.google.com by jpran...@gmail.com on 31 Mar 2010 at 11:34

[GoogleCodeExporter]

Original comment by jpran...@gmail.com on 1 Apr 2010 at 5:29

• Changed state: Started

[GoogleCodeExporter]

Fixed in r2951 and added tests in r2952.

Original comment by jpran...@gmail.com on 13 Apr 2010 at 11:48

• Changed state: Done

[GoogleCodeExporter]

This issue is included in RF 2.5 alpha 1.

Original comment by jussi.ao...@gmail.com on 6 May 2010 at 1:35

• Added labels: alpha1

[GoogleCodeExporter]

Original comment by pekka.klarck on 6 May 2010 at 4:15

• Changed title: Using a timeouted keyword with wrong number of arguments causes FrameworkError