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.

Sign up for GitHub

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

Jump to bottom

Future development to support RF >3.2 #413

Open
test-fullautomation opened this issue Dec 16, 2020 · 75 comments
Open

Future development to support RF >3.2 #413

test-fullautomation opened this issue Dec 16, 2020 · 75 comments

Comments

@test-fullautomation
Copy link

test-fullautomation commented Dec 16, 2020 •
edited
Loading

Dear reader,

I try to use RobotFramework 4.0b1 and latest RED, but unfortunately it seems that it doesn’t load the Builtin-Libraries.
E.g. it writes “unknown keyword ‘log’”.
Unchanged workspace with e.g. 3.2.1 RobotFramework works without issue.

I’m happy for any idea how to solve this issue because I would like to stay with the 4.0 version.

Thank you,
Thomas

This is related to:
https://forum.robotframework.org/t/red-doesnt-find-builtin-libraries-with-robotframework-4-0b1/1100/3?u=thpoll
@michalanglart
Copy link
Collaborator

Hi,

RED does not support RF 4.0 yet

@Snooz82
Copy link

Snooz82 commented Dec 16, 2020

@michalanglart
the Beta1 should be in a state that you can have a look how it is build.

you basically have to maintain two things.

first:

elements are now all packet into on node. (so /keywordspec/keywords/kw)
is in

Arguments are not longer a list of string representations. they are now structured.

But you can just access the //arguments/arg[repr] attribute. It will contain same content that was before in 

<kw name="Click" source=".pyenv/versions/3.8.0/lib/python3.8/site-packages/Browser/keywords/interaction.py" lineno="252">
            <arguments repr="selector: str, button: MouseButton = left, clickCount: int = 1, delay: timedelta | None = None, position_x: float | None = None, position_y: float | None = None, force: bool = False, noWaitAfter: bool = False, *modifiers: KeyboardModifier">
                <arg kind="POSITIONAL_OR_NAMED" required="true" repr="selector: str">
                    <name>selector</name>
                    <type>str</type>
                </arg>
                <arg kind="POSITIONAL_OR_NAMED" required="false" repr="button: MouseButton = left">
                    <name>button</name>
                    <type>MouseButton</type>
                    <default>left</default>
                </arg>
                <arg kind="POSITIONAL_OR_NAMED" required="false" repr="clickCount: int = 1">
                    <name>clickCount</name>
                    <type>int</type>
                    <default>1</default>
                </arg>
                <arg kind="POSITIONAL_OR_NAMED" required="false" repr="delay: timedelta | None = None">
                    <name>delay</name>
                    <type>timedelta</type>
                    <type>None</type>
                    <default>None</default>
                </arg>
                <arg kind="POSITIONAL_OR_NAMED" required="false" repr="position_x: float | None = None">
                    <name>position_x</name>
                    <type>float</type>
                    <type>None</type>
                    <default>None</default>
                </arg>
                <arg kind="POSITIONAL_OR_NAMED" required="false" repr="position_y: float | None = None">
                    <name>position_y</name>
                    <type>float</type>
                    <type>None</type>
                    <default>None</default>
                </arg>
                <arg kind="POSITIONAL_OR_NAMED" required="false" repr="force: bool = False">
                    <name>force</name>
                    <type>bool</type>
                    <default>False</default>
                </arg>
                <arg kind="POSITIONAL_OR_NAMED" required="false" repr="noWaitAfter: bool = False">
                    <name>noWaitAfter</name>
                    <type>bool</type>
                    <default>False</default>
                </arg>
                <arg kind="VAR_POSITIONAL" required="false" repr="*modifiers: KeyboardModifier">
                    <name>modifiers</name>
                    <type>KeyboardModifier</type>
                </arg>
            </arguments>
            <doc>Simulates mouse click on the element found by ``selector``.</doc>
            <shortdoc>Simulates mouse click on the element found by ``selector``.</shortdoc>
            <tags>
                <tag>PageContent</tag>
                <tag>Setter</tag>
            </tags>
        </kw>

@michalanglart
Copy link
Collaborator

Thanks René @Snooz82!

I had a look. It does not seem complicated too much although we cannot just change our existing implementation as we did between version 1 and 2 of specifications as the structure changes too much. Since we want to support both 3.x and 4.0 we need to provide two implementations and hide them behind the interfaces so that they would behave the same from the perspective of the code which uses that.

@test-fullautomation
Copy link
Author

Hi both,
thank you for your comments.
Looks like I wait for a solution for this issue.
Please inform me when a solution is there. I would support testing. You can also give me test builds.
Thomas

@michalanglart
Copy link
Collaborator

Ok, sure. We can provide you with the test builds

@zied-cision
Copy link

Hello guys, any news for supporting RF 4.0 ?

@michalanglart
Copy link
Collaborator

Hi,

I hope the support to some extent should be possible probably around the time RF 4.0 would be released. However I'm not sure yet about handling all the new syntax.

@adrianyorke
Copy link

adrianyorke commented Mar 4, 2021 •
edited
Loading

Hi team,

We were researching for known compatibility challenges with RF 4.0 + RED and we discovered this issue.

One of our testers was having a problem specifically with RF 4.0b3:
image

Let me know if this is a different problem and I will raise a separate issue.

RF 4.0 officially releases next week although it will be a while yet before our company adopts RF 4.0 as the default version.

Are you able to indicate when RED might have a compatible version?

Thanks,
Adrian

@michalanglart
Copy link
Collaborator

Can't tell now, sorry.

We're very busy with other projects currently. We should have some time for RED in coming weeks and some work was already done for RF 4.0 but as of now I don't know yet how much work is needed.

@Lokeshwaran21
Copy link

Robot Framework 4.0 is a new major release with lot of big new feature, Please Make RED supporting RF 4.0 ASAP

@zied-cision
Copy link

UP

You made an excellent work on RED guys, it's really got the best UX for Robot.
Unfortunately, we couldn't upgrade to RF4 until RED fully support it.

@adrianyorke
Copy link

adrianyorke commented Mar 24, 2021 •
edited
Loading

UPDATE: Robot Framework 4.0 was officially released 11.3.2021:
https://github.com/robotframework/robotframework/releases

@michalanglart : I believe there be a few changes for RED in order to be compatible with RF 4.0. Is there anything the community can do to help? Post it here and you might get support.

@rikardndreu
Copy link

We are stuck on robotframework 3.2.2 and hopefully RED will support 4.0 soon.

Cheers.

@ericbjones
Copy link

+1 add RED support for RF 4.0 🙏 🙏

@DanielPenning
Copy link

+1 add RED support for RF 4.0.

RED is such a useful tool, but RF 4 brings a ton of useful features so upgrading is quite appealing.

@luqi-qa
Copy link

luqi-qa commented Apr 5, 2021

+1

Can't wait for RED support with RF4

@Loverineaux
Copy link

+1
Please add support for RF 4.0 in RED

@otemek
Copy link

otemek commented Apr 16, 2021

+1
Please?

@liangwang-syton
Copy link

+1
Can't wait for RED support with RF4

@jmarcedwards
Copy link

+1
Yet another shameless plug for RF4 support in RED.
"Love the RED!"

@abdou-rajawi
Copy link

+1

Add RED Support with RF4 Please.

@IanBingWu
Copy link

+1

Add RED Support with RF4 Please.

@WingTelexis
Copy link

#421 (comment)
An official message that they will start development for RF4.0 👍

No, there is no solution until RED will support RF 4.0

The PR 418 will only make this exception disappear but there are more changes in RF 4.0 which requires RED to change in order to properly run tests.

We're about to start development for RF4.0

@liangwang-syton
Copy link

活捉老乡一枚 @IanBingWu

@Zeckie Zeckie mentioned this issue May 7, 2021
Closed
@vvelusamy1
Copy link

i hope RED development started already. Expecting the fixed version of RED sooner so that we can move to make use of RF 4.x

@zied-cision
Copy link

Same here.

@Tim-QA
Copy link

Tim-QA commented May 19, 2021

Can someone from the development team please tell us the current status and when will Red be supported

@adrianyorke
Copy link

For those of you following this issue, if your needs are urgent then you may wish to explore alternatives until RF4 compatible RED becomes available.

One popular alternative is Robot Framework Language Server which is available as an extension in VS Code:
https://robocorp.com/docs/developer-tools/visual-studio-code/lsp-extension#what-is-the-language-server-protocol-lsp-and-why-is-it-useful

@valentijnpeters
Copy link

How can we help to make RED available for RBFW 4?

@Tim-QA
Copy link

Tim-QA commented Jan 20, 2022

Also from my side please keep-alive RED.

@michalanglart
Copy link
Collaborator

@Snooz82 Yes, it is in deep hibernation for now. In past we had few persons working on it full time. Now from old team there are just 2 of us still in company - myself and our great tester @joanna-may . We were assigned however with different projects which occupies us 100% or even more (in my case much more).

I do like this project and I would be happy to work on it but the reality is that I simply do no have time for it now.

Having said that: we found a person which should be able to spent some time with RED - but firstly needs to be introduced and needs to explore the code a little bit.

@nanduIyer
Copy link

nanduIyer commented Jan 20, 2022 via email

@NikitaOstr
Copy link

@Snooz82 Yes, it is in deep hibernation for now. In past we had few persons working on it full time. Now from old team there are just 2 of us still in company - myself and our great tester @joanna-may . We were assigned however with different projects which occupies us 100% or even more (in my case much more).

I do like this project and I would be happy to work on it but the reality is that I simply do no have time for it now.

Having said that: we found a person which should be able to spent some time with RED - but firstly needs to be introduced and needs to explore the code a little bit.

We all cross fingers!!! Good luck and waiting for any news from you guys !

@adrian-evo
Copy link

While I agree that RED had his value in the past, when we had no other good enough alternatives, I don't agree that today this will be a big loss for our community. I agree it is difficult to switch to another way of working after many years, but this is just an IDE and it is not justifiable to use old RF 3.x just for the sake of using a familiar IDE, when you can switch to RF 4.x and use a more modern IDE, like Visual Studio Code or Pycharm as you like, i.e. any IDE supported by Robocorp company.

@everlighting
Copy link

Any updates team?

This was referenced May 7, 2022
Open
Closed
@Zeckie
Copy link

Zeckie commented May 7, 2022

The scope of this issue has expanded from when it was originally created. Would it be possible to change the title (something like Future development of RED to support Robot Framework > 3.2) and pin it to the top of the issues list?

@michalanglart michalanglart pinned this issue May 13, 2022
@michalanglart michalanglart changed the title RED doesn't find Builtin-Libraries with RobotFramework 4.0b1 Future development to support RF >3.2 May 13, 2022
@Zeckie Zeckie mentioned this issue May 18, 2022
Open
@NikitaOstr
Copy link

@michalanglart Hi Michal! Do you have any ETA, if exist, to starting to work on supporting RF4 and above? Please!!!!!

@michalanglart
Copy link
Collaborator

Hello. I still cannot offer any timeline. I'm currently not involved however only some limited work was done recently and it was not yet about the changes in the code but rather setting up the environments for building & automated tests.

I'll let you know once it would be clear what's in the future with RED

@everlighting
Copy link

Any updates @michalanglart

@NikitaOstr
Copy link

Hello. I still cannot offer any timeline. I'm currently not involved however only some limited work was done recently and it was not yet about the changes in the code but rather setting up the environments for building & automated tests.

I'll let you know once it would be clear what's in the future with RED

Hi Michal! What do you think about sharing your tasks to our community? I'm sure we have here a lot of professional programmers that can contribute to our RED, what do you think? Perhaps this is our last chance to push it from that dead point)

@valentijnpeters
Copy link

valentijnpeters commented Sep 16, 2022 via email

@NikitaOstr
Copy link

NikitaOstr commented Sep 17, 2022 •
edited
Loading

Install Microsoft Visual Studio and try Robot Framework with it. You will be astonished! You will be blown away! Furthermore, you don't even want to ever revert to Eclipse.

I really tried MVS but did not find two mandatory things to me (PyCharm and Eclipse have those features):

  1. running test/suite from configurations by hitting play button
  2. full debug run with breakpoints
    Can you share how to configure all this staff in MVS please?
    Also, are you sure about MVS and not VSCode?

@Snooz82
Copy link

Snooz82 commented Sep 17, 2022

Dont use Visual Studio.

use VSCode!
with the Plugin RobotCode which has debugging and running tests with a play button.

@avancil
Copy link

avancil commented Sep 22, 2022

I use Eclipse, and am sad that this plugin doesn't work with current Robot versions. My workaround for now is to use https://github.com/NitorCreations/RobotFramework-EclipseIDE which at least gives me syntax highlighting. It doesn't give an outline, definition lookup, debugging, or much of anything else, but at least I can read the files.

@valentijnpeters
Copy link

valentijnpeters commented Sep 22, 2022 via email

@everlighting
Copy link

we can pause execution in between in red but vs code i don't see that option @valentijnpeters
@michalanglart any updates?

@AshaSaxena11
Copy link

Visual studio code is i=not recognizing variable outside robot file , like if variable is defined in python file ,VScode is not able to recognise it

@valentijnpeters
Copy link

valentijnpeters commented Nov 20, 2022 via email

@rokajozsef
Copy link

Sorry @Snooz82 and @valentijnpeters , but in my opinion VSCode with RobotCode extension is not better than RED. I tried more other Eclipse, PyCharme and VSCode extension, but there is one problem where they all fail:

  • If I use a keyword, which has an argument, and I add there an other keyword, navigation and autocomplete doesn't work with/on the other keyword, e.g.:

Keyword1 arg1=sthing arg2=Keyword2

So I use RED for coding and PyCharm for running :/

@petr-ixi
Copy link

@michalanglart or anybody else, is there at least small chance to update to newest Robot framework? Please, this is great tool you created and would be really sad to leave it.

@valentijnpeters
Copy link

valentijnpeters commented Jun 3, 2023 via email

@michalanglart
Copy link
Collaborator

@michalanglart or anybody else, is there at least small chance to update to newest Robot framework? Please, this is great tool you created and would be really sad to leave it.

I don't think the project will be actively developed within company anytime in the future unfortunately.

@valentijnpeters
Copy link

valentijnpeters commented Jun 26, 2023 via email

@Daniwin82
Copy link

Daniwin82 commented Jun 27, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests