Is Robot Framework better than Selenium?

Is Robot Framework still used?

I'm currently working in a small organization that's using robot framework for it's automation tests.

The issue is that our project is still using a mixture of Jython and Ruby scripts. We now realize we are also using the robot framework.

For a long time, I thought the robot framework was just a tool for test automation (that's what it's documentation claims), but obviously I was wrong, and the documentation is even wrong. The question is, where is the correct place to use Robot Framework? Is it possible to use the framework in both Jython and Ruby scripts? I don't want to have to change all of the files that make the automation, especially when most of our files are made in Jython. Thank you. If I understood correctly you already have some tests made in robotframework/Jython (in your case probably in Python Script)? Is that your case? And in this case, your question is already answered on the official website : If your goal is just automation, then you should not worry about how your code is made. Just focus on your tasks to be done (and in what order).

I would think on your Jython file (because I know robotframework/Jython is a mix of Jython and python) you could make as many classes (with their parameters) as you like in order to reuse the code and avoid repeating yourself. But don't forget about the imports (I would say that robotframework/Python is only "half-implemented").

Is Robot Framework better than Selenium?

I have done some Selenium programming for automated testing.

Since Robot Framework is much easier to learn (or so it seems to me) I thought of switching to Robot Framework since it can also be taught to write tests by following the online tutorials.

So I'm asking whether Robot Framework is better than Selenium. It doesn't have to be a simple comparison - I'm looking for more of a general view, which technology is worth learning? Any experienced Robot Framework users out there who can share their opinions? Thanks! EDIT: To make it clear, I'm not interested in comparing the functionality of both frameworks per se. I'm more concerned about which one is worth trying out, if one at all.

RobotFramework definitely is a lot easier to learn and get into coding. If you are coming from selenium, the framework makes it rather easy to pick up, no matter how long you have been writing this particular scripting language (so called webdriver technology). If you have any experience with jinja or python you are well equipped to start. What you are really looking for in a tool of course is the ability to do things automatixcally without too much human interference. That's mainly the advantage of using robots. So you might want to investigate a bit what other projects that have used robots have built themselves to do that they don't need the "human" input.

Why not use Robot Framework?

I don't have any personal experience with it, but I see it being useful in many situations.

I also see some drawbacks that make me question it's value. In addition, it appears to be quite new.

Advantages: It has a plugin-based architecture, which allows for a lot of customisation. It can be used to write tests that are both maintainable and readable. Disadvantages: I feel like it could be a bit slow. It takes a bit of time to figure out how it works and get used to it.

I haven't found any examples that actually use it for testing. In the end, I'm not sure if it will be useful or not. It seems a bit complex. I would love to hear if anyone uses it or if they have any experience with it.

Note: I only ever use Test Complete for testing. I use it because it is fast and it works.

Test Complete, the other product. My personal experience with Test Complete is very similar. It took a while to get used to it. I initially wasn't really sure if it was going to be useful or not. The only advantage I saw was that it was fast, but I didn't find any examples where it was used for testing. I did find a few blog posts about people using it for testing, but they were mostly about people using it for writing automated tests.

Over time, I figured out how it worked and I started using it for testing. It is now my preferred tool for testing, even though I don't really know why I use it.

It is extremely fast. It can run your entire suite in under 3 seconds, which is amazing.

It has an extremely powerful set of features. I don't have enough space to list them all here.

It is expensive. It can be confusing to use at first. You need to learn how to use it.

It doesn't seem to have a community around it. I haven't seen any examples of it being used for testing.

As you can see, there are a lot of similar things between the two products. Why do these tools work?

What is Robot Framework used for?

Introduction.

If you're new to automated testing, then you're likely wondering what tooling you should be using to carry out your tests. This guide aims to give you a high level overview of Robot Framework and the reasons why you should be using it, so that you can get started right away. If you want a fuller introduction to Robot Framework, then my blog post on the subject is a good place to start.

I've also included a link to the Robot Framework documentation at the end of this post. I will use this link to refer to the Robot Framework documentation throughout the rest of this post.

Why use Robot Framework? There are a number of reasons to use Robot Framework over traditional testing tools, such as an IDE. To name but a few: Robot Framework has built in support for running unit tests, functional tests, integration tests, load tests, and acceptance tests. This means that you don't have to install any new plugins or add any extra dependencies to run your tests - it will just work.

It runs tests on many different platforms including Windows, Mac OS X, and Linux. Robot Framework is very configurable, giving you full control over how your tests are run. You can define tests to be run in parallel, run them sequentially, or even run just a few tests at a time, if necessary.

Robot Framework also allows for easy reporting. It can record the output of each run, which you can then analyse later, or simply output it to a file to save as a human readable report.

Robot Framework is integrated with Jenkins and Travis CI, meaning that you can easily set up builds whenever you need to see if any of your tests fail. The Robot Framework user interface (UI) is easy to learn, especially for newcomers. Robot Framework supports running test suites, not just single tests. This means that you can run all of your unit tests from one point, ensuring that they're all passing.

Robot Framework is cross-platform, meaning that it will run on almost any type of hardware. So why not use Python? If you're a beginner to writing automated tests, then you're most likely only familiar with basic Python programming.

Related Answers

What is autonomous systems in mechanical engineering?

Autonomous systems are systems where all the processe...

What is autonomous systems in robotics?

It's all over the internet, so we're giving you the basics for unde...