Skip to content
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

Closed
adam-wypych opened this issue Apr 3, 2018 · 3 comments
Closed

Planned changes in RF 3.1, which affects RED #200

adam-wypych opened this issue Apr 3, 2018 · 3 comments
Assignees
Milestone

Comments

@adam-wypych
Copy link
Contributor

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:

  1. Debugger: Possibility to separate library and user keywords in listeners and in model objects robotframework/robotframework#2297 libname is used in debugging context
  2. New way of accessing variables: Access variables in certain resource or variable file using ${my_resource.My Variable} syntax robotframework/robotframework#1999
  3. Robotic Process Automation: Terminology configuration to support usage in generic automation robotframework/robotframework#2788 ( new Tasks table )
  4. Embedded keywords with list and dictionary: Support literal list/dict syntax when using @{list} and &{dict} as embedded arguments robotframework/robotframework#2699
  5. For Loop (new separator for not pipe separated format): For loop syntax enhancements robotframework/robotframework#2783
  6. Remove of some deprecated syntax:
    a) 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#2263
    d) Metadata and User Keyword table names removed: Deprecate Metadata and User Keyword table names robotframework/robotframework#2208
    e) Deprecate Document and Suite/Test Pre/Post Condition synonym settings an error now: Deprecate Document and Suite/Test Pre/Post Condition synonym settings robotframework/robotframework#2207
    f) 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 old Meta: Name syntax for specifying test suite metadata robotframework/robotframework#1918
  7. Python 2.6 and Python 3.4 will be not supported - it looks like the feature to inform about this in case user has wrong version: Remove support for Python 2.6 and 3.3 robotframework/robotframework#2276
@KrzysztofJozefowicz
Copy link
Contributor

Thanks Adam, we will add those RF 3.1 tasks to backlog for analysis.

@hugovk
Copy link

hugovk commented Apr 11, 2018

Correction to:

  1. Python 2.6 and Python 3.4 will be not supported

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
@michalanglart michalanglart added this to the 0.8.9 milestone Oct 23, 2018
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
@michalanglart michalanglart self-assigned this Nov 20, 2018
@michalanglart
Copy link
Collaborator

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
Projects
None yet
Development

No branches or pull requests

4 participants