SAP Enterprise Portal + Automated Functional Testing – Part 7 of …

In anticipation of posting about a new topic I’m going to wrap up my Watir Automated testing posts with a few more top tips.

TOP TIP – How do I run a single test?

So you have lots of tests in your test suite but only want to run one? No need to create an ad-hoc test case, simply pass in the –name parameter when running the test:

ruby test_mytestcase.rb --name test_just_this_method

TOP TIP – How do I run the test in background mode?

Running the test so you can see what is going on in the browser is sometimes useful but most of the time you’ll want to run the tests in the background and just see the results. This is easily done by passing the -b parameter on the command line:

ruby test_mytestcase.rb -b

TOP TIP – Helper methods

I have a couple of helper methods which I use in most of my test cases:

def should_find(find_me)
assert(@ie.contains_text(find_me), "*\n*\n*\nText not found: #{find_me}\n*\n*\n*")
end

def should_not_find(find_me)
assert_nil(@ie.contains_text(find_me), "*\n*\n*\nFound text which should not be present: #{find_me}\n*\n*\n*")
end

No clever code here it just means I can write tests which are easier to read:

should_not_find("Portal Runtime Error")
should_find("Success")

FIN
Well I’m running out of content about testing as you can probably tell! So I guess that’s a wrap. I’ll no doubt re-visit automated testing again at some point but for now that’s my lot.

NEXT TIME
I’ve been working on creating web services for Enterprise Portal and calling those web services from Microsoft .Net. I’ve taken lots of notes, so expect a series of EP web services posts real soon.

Ruby unit testing – run only one test

If you don’t wish to run all the unit tests in your test case you can tell ruby to run only one by passing in the name of the test:

  ruby test_mytestcase.rb --name test_just_this_method

Ruby testing – setup project folders

Its a good idea to keep your test cases seperate from your production code:

  myproject
      lib/
          workomatic.rb
      test/
          test_workomatic.rb

When you have your project setup in this way add the following line to the top of your test cases:

Inside test_workomatic.rb

  $:.unshift File.join(File.dirname(__FILE__), "..", "lib")
  require workomatic.rb

SAP Enterprise Portal – Automated Functional Testing – Part 6 of …

Time for some more tips. I had a comment on my last post asking how to navigate around the portal so lets start there.

TOP TIP – How to navigate the portal
So how do you navigate around the portal using the menu? Simple you don’t! I found there are lots of problems using the portal menus due to the number of frames used so I simply jump directly to the URL of the PAR file I am testing. Here is a typical test:
def test_typical
    # My Helper method which logs in using the given user id and password
    logon("myuserid", "mypassword")

    # Go directly to the URL of the PAR I want to test
    @ie.goto('http://portal:50000/irj/servlet/prt/portal/prtroot/uk.ac.ncl.testing.ISRPageProcessor')

    # do tests here
end
Ok that’s fine but how do you find the direct URL of the PAR file you want to test? Ahh thats were my next top tip comes in.

TOP TIP – How to find the direct URL of a PAR file
Open up the SAP Netweaver Developer Studio

Open your project

Open the file:
MyPortalProject
    dist
        PORTAL-INF
            Portalapp.xml
You should now see a “Run…” button for each portal component in your project

Click the “Run…” button and the dev studio will open up a new browser window with the URL of your PAR file. Now simply use this URL in your test scripts.

COMING UP IN PART SEVEN
Short and sweet but at least I’m posting more often. Next time… You guessed it more top tips!

SAP Enterprise Portal – Automated Functional Testing – Part 5 of …

Ok last time I promised some hints and tips so lets begin. I’m going to keep the hints and tips posts fairly short in the hope it will encourage me to post more often. I received a comment on my last post asking how I find the ID/Name attributes of my forms so I though that would be a good place to start.

TOP TIP – How to find ID/Name attributes of a form
To save me having to sifting through the html code of a page for the ID/Name of a control I use the FireFox browser with the Web Developer Toolbar extension installed. The Web Developer Toolbar is a great time saver not only for finding out form details but it has lots of other features too, I strongly recommend you check it out.

When you have the Web Developer Toolbar installed under the Forms menu you have the Display Form Details option, simply select this option and the page will be highlighted with yellow tags showing the ID/Name attributes of each item on the form.

NOTE: Forms items which are created using HTMLB do not get a static ID/Name attribute these attributes appear to be generated each time the page is created. If this is the case how do we write tests against HTMLB forms? That’s were the next top tip comes in…

TOP TIP – Writing Watir test against HTMLB forms
As I mentioned above HTMLB forms do not have a static ID/Name attribute, they are generated each time the page is created so you will find your HTMLB form controls will have an ID/Name of something along the lines of “htmlb_18528_htmlb_9998_3” if you then reload the page the ID/Name attributes will have changed i.e. “htmlb_18328_htmlb_9991_1”. This means the following Watir test code would not work as each time the page reloaded the :id attribute would be different.

@ie.text_field(:id, 'htmlb_18528_htmlb_9998_3').set('test me')

So how do we get around this? Well the best way I have found is to use Watir’s :index parameter when accessing form controls. The :index parameter works by sequentially counting form controls from left to right top to bottom. So to set the text of the second control on the page we use the following code:

@ie.text_field(:index, 2).set('test me')

This is not an ideal solution due to the fact if you change the layout of the page your index’s will also change and break your tests. However I’ve been using this method for a while now and it’s never been a major problem, besides I’m not sure how else it could be done!

COMING UP IN PART SIX
Well that post turned out to be slightly longer than I planned, so much for keeping these tips short. Next time more of the same.

SDN Blog

I was recently invited to start a blog on the SAP Software Developers Network (SDN). So I’ve written a series of posts about Automated Functional testing the SAP Portal using Watir:

SDN Blog

Introduction
Automated Functional Testing – Part 1 of …
Automated Functional Testing – Part 2 of …
Automated Functional Testing – Part 3 of …
Automated Functional Testing – Part 4 of …

IMHO worth a look if your interested in testing your SAP Portal. I’ll start posting the rest of the series on here from now.

Ruby unit tests – run only one test method

What if you don’t wish to run all the unit tests in your test case?

You can tell ruby to run only one test method by passing in the name of the test:

  ruby test_mytestcase.rb --name test_just_this_method