-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Planned changes in RF 3.1, which affects RED #200
Comments
Thanks Adam, we will add those RF 3.1 tasks to backlog for analysis. |
Correction to:
Python 2.6 and Python 3.3 will be not supported |
KrzysztofJozefowicz
pushed a commit
to KrzysztofJozefowicz/RED
that referenced
this issue
Aug 21, 2018
- WITH NAME can be written in upper case only Change-Id: I8aaee6e11c27d27294201e2bf624ab2f26d548da
KrzysztofJozefowicz
pushed a commit
that referenced
this issue
Aug 22, 2018
- WITH NAME can be written in upper case only Change-Id: I8aaee6e11c27d27294201e2bf624ab2f26d548da
red-common-CI
pushed a commit
that referenced
this issue
Sep 28, 2018
- handling deprecated/removed settings names (general/keyword/test case)
red-common-CI
pushed a commit
that referenced
this issue
Sep 28, 2018
- review fixes - removing not needed test helpers
red-common-CI
pushed a commit
that referenced
this issue
Nov 20, 2018
The arguments descriptor is now able to support function annotations properly
red-common-CI
pushed a commit
that referenced
this issue
Nov 20, 2018
- upper cased FOR is also recognized as for-loop (previously it had to be :FOR) - validation reports deprecated API for IN/IN RANGE/... written differently than in canonical form
red-common-CI
pushed a commit
that referenced
this issue
Nov 20, 2018
- fixes for minor issue found in test - those should close RED-733
Support for RF 3.1 was released in RED 0.8.9 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Good morning,
I read the topic made by Pekka about planned changes in the next major release of RF 3.1: https://groups.google.com/forum/#!topic/robotframework-users/vMbcUF83Tqc .
After follow or issues releated to RF 3.1 milstone, I identified few of them which affects RED a specially:
${my_resource.My Variable}
syntax robotframework/robotframework#1999Tasks
table )@{list}
and&{dict}
as embedded arguments robotframework/robotframework#2699a) Remove possibility for specify custom timeout message not implemented: Remove possibility to specify custom timeout message robotframework/robotframework#2291
b) Library with space are will be an error: Deprecate importing library with extra spaces in name robotframework/robotframework#2264
c) WITH NAME only accepted with uppercase: Deprecate using
WITH NAME
case-insensitively robotframework/robotframework#2263d) Metadata and User Keyword table names removed: Deprecate
Metadata
andUser Keyword
table names robotframework/robotframework#2208e) Deprecate
Document
andSuite/Test Pre/Post Condition
synonym settings an error now: DeprecateDocument
andSuite/Test Pre/Post Condition
synonym settings robotframework/robotframework#2207f) Deprecate using same setting multiple times: Deprecate using same setting multiple times robotframework/robotframework#2063
g) Deprecate old
Meta: Name
syntax for specifying test suite metadata: Deprecate oldMeta: Name
syntax for specifying test suite metadata robotframework/robotframework#1918The text was updated successfully, but these errors were encountered: