Please post your Web Driver questions in official Web Driver forum

Saturday, July 24, 2010

Test Automation Recovery Scenarios: how much recovery

This article is not specific to QTP but elaborates a more general problem with functional test automation. I caught the fancy of recovery scenarios when came across such feature in QTP. QTP's motive is to recover from problems of unexpected pop up windows (though concept itself is contradictory and requires you to know object properties of unknown window in advance!) .Though soon realized that it is more of marketing gimmick than of being of much importance to automation it self. Some thing which always puzzled me was how much of such scenarios to use.
While under going In house QTP training we were told to even check presence of objects before exercising them. This is to make sure that QTP does not throw any pop up error during test case execution. (at least this is what we were told during training). Later I realized that using QTP properties could be to order QTP do what is intended (though in a limited manner).
This idea of checking every object before test freaked me out. I started wondering if I have to check each object first before I perform any operation. Being a Selenium enthusiast I started doing some thing like -

public safeType (String obj, String testData) {
       selenium.type(obj, test Data);
       Reporter.log("Element: " +obj+ ", NOT found")

But then came across Unchecked Exception in java, and realized that non availability of object on page should be treated as run time exception and test automation should not make efforts to come out of these exceptions. But then I thought that "safe" approach could be used for non mandatory fields/tests on a page which would post error on test report but will let tests continue the execution. (Remember unavailability of an element makes entire tests stop in selenium). Well I am not sure how practical this approach is but I am curious to know how you would have approached it.

Friday, July 23, 2010

"Loading......." the contents

Came across a testing blog yesterday and started browsing all past blogs of it using calendar.
Look like my network is slow and I got to see "Loading...." message after clicking on calendar link. I collapsed the link and clicked on calendar again and got to see "Loading....... Loading.......". Each collapse and expansion of calendar increases the message "Loading......."  by count one.

After a few clicks

After a few more clicks

Thursday, July 22, 2010

So why did you write "this" certificate?

This is going to be an eternal post which I would modify as and when I find new reasons for writing certificates.
Though I personally don't admire certificates but happened to write one (QC 9.2) on my own. This happened last year when I was told about a project which needed experience on QC and client had asked have QC certified resource working on it. Well exam was really easy and I happen to clear it. Irony is project never materialized and I never got to work on QC. Happened to mention about certification on my resume and under the influence of this group removed it.

Of late I have been interviewing testing candidates and a few of them have certification batch with them. And we all know most famous certification batch in market is ISTQB (I must appreciate their marketing for sure and hope they contribute a share of their earnings to some open source testing projects. Though I am not very hopeful of this.).

I am listing here the responses I receive from the candidates -
  1. One candidate having more than 2 years of  experience said - "I wanted to learn testing concepts". My response - "So you were not aware of testing concepts for past two years". I can't recall the response of Candidate.
  2. One candidate said - "I have written foundation level exam for ISTQB". My question - "So what did you learn?". Candidate - "Nothing much but I am planning to write advance level and would definitely learn from it." !@#!@#!@#!$@$$!@
  3. Another candidate said - "Certification fetches you better salary", I can only imagine how much money I have lost so far.
This is an incomplete blog and would update this when I receive new answers.

So how do you Strategize it?

Happened to read Pradeep's blog today and got enthusiastic to write a blog. Found there is a intricate situation for me to blog about, and almost all of us would have faced it some time.

Of late I was called by one of the engagement manager to help one tester (the lone warrior and new joinee to organization) in project to help him on test strategy. Had a meeting in the after noon with project team and got to know that team has least information on project (assignment had begun a week ago). Project is a migration task from one java technology to other and testing activities would involve function testing (with no definition of scope) followed by performance testing. Team is bewildered as they have least information about project whereabouts and the tester has no idea on how he would carry out functional and performance testing. On top of this the very first deliverable for the project is test strategy document.

So our warrior has been asked to come up with test strategy. And he indeed developed a test strategy document on the basis of general info and experience ha has gained over years. The document does not consist any specific attribute to project (for obvious reasons). Now engagement head is not happy with length of document as this is a deliverable which is going to bring more money and probably more business. He believes that it has to have more info. I don't question him for his opinion as his objective is to get more business to company may be right from his perspective.

So what I did? Well first of all I consoled the poor tester who was feeling left out. A new joinee having feelings of not being able to live up to responsibilities of his first job. Besides this only option I could think of was questions, zillions of questions to be asked to client as we had least info about the project. I had a dedicated section added to doc about questionnaire which we had to know before having the testing assignment begun. He added a couple more pointers about exit and entry criteria for each phase of functional and performance testing. The document is sent to supervisor and review comments are awaited.

So what different would you have done in this situation?

Wednesday, July 7, 2010

Selenium - Stack Exchange website

Please support Selenium's own website on Stack Exchange here -

Saturday, July 3, 2010

Hacking Website from Google

If u have not yet seen this!
Google labs is offering a sample application with security vulnerabilities. I have just started browsing through and its very interesting. More interesting for some one who is new to Security Testing.
Website is available here and open to all for hacking with tips and tricks provided by none other than Google itself.
Fork me on GitHub