Oh Robot, wherefore art thou Robot?

Manual testing.  Yes – I said it, manual testing.  In my career as a QA professional, I have more than certainly done my fair share of it.  The best scenario was eloquently designed test scenarios that flowed smoothly and left no ambiguity as to what the desired test results should be.

The worst was the complete lack of any documentation whatsoever, and without documentation as a backbone for software development, any defects were poo pooed and marked as By Design.
As I said, I’ve seen my fair share of manual testing, and it is the complete boredom from that type of testing that has sparked my desire to better understand and embrace Robot Framework as a viable solution to test automation.

I’ve used Selenium IDE, WAPT, and a few others, but what attracted me most to RF was its simplicity.  It is structured in a way that makes sense to me, so that makes it a great tool in my book.
Let’s take a look at what a simple test looks like:

*** Settings ***

Documentation  my first test

Test Teardown Close All Browsers

*** Variables ***
${URL} http://Google.com
*** Test Cases ***

Open browser  ${URL}

Capture page screenshot

Close browser
There!  That is a very simple test case that when executed will open the default browser of the system it is executed on, go to Google, and capture a screenshot!
After executing, RF provides results through an easy to read report and log.


As I delve deeper into this subject and learn more I will share my experiences, good and bad!

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s