The Foobars

Robot framework is an extensive and widely used test automation framework which (along with RIDE) gives you an easy to use and easy to navigate interface and neat style IDE to its users. It has huge support for a variety of external and internal libraries for keywords support, using which user can develop new high-level keywords using the existing one. Since Robot is an open source verily used framework you can find its detailed documentation from GITHUB (( https://github.com/robotframework/robotframework )) to know more about it. (It’s not just detailed but good to understand as well). In this article, I’ll share ‘How to setup Robot framework & RIDE IDE to write and execute your testcases in an easy and tabular manner’. To setup and configure the Robot framework correctly you will be needing installation of the following software and tool. 1.        Python. 2.        Iron Python. 3.        Robot Framework. 4.        Element Tree. 5.        RIDE. 6.        WX

The automation toolchain of the continuous integration begins with continuous integration in the version control system. Continuous Integration is a confusing topic to some, because, most believe that it has something to do with initiating the resource deployment once team has  built the project . But the story doesn't start there, the story starts at the moment someone hits "git push" -- or any similar alternate resource versioning tool (such as SVN). The main primary focus of continuous integration, and continuous deployment is to automate the process of software release. Removing the wait times needed by the teams for operations team wait time in order to maximize the output of the development teams. Sometimes this is termed under the umbrella of  DevOps . DevOps is a huge and complex concept in itself, and most of the times DevOps is also misunderstood just like continuous integration. Anyways, continuous integration is only a single step in the long running DevOps