Skip to main content

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.

Comments

Popular posts from this blog

Return only first or last element from webelements collection

We often come across situation when there are multiple elements on a page and we probably like to exercise only a few of them using selenium webdriver. May be just first and last element. For example on a search result page we may like to click on only first and last link and not all. This is when Iterables API comes handy. (By the way I am assuming that you have already completed watching selenium training videos :)). Once we have collection of web element then we can use Iterables to get only first or last element as following - Consider that we fetch collection of element as - List< WebElement > webElements = getDriver().findElements(By. id ( "htmlID" ));   Now we can get the first web element from this collection as -  WebElement firstElement = Iterables. getFirst (webElements,  getDriver().findElement(By. id ( "defaultElement" )));   Herein second argument -   (getDriver().findElement(By. id ( "defaultElement" )))    in the me

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro

Using xPath to reach parent of an element

Well, I am big fan of css locator my self there are times when css locators don't fit requirement. One such requirement is when you want to navigate to parent element of an element and may be parent of parent and even more. Unfortunately css locators don't provide any mechanism to navigate to parent of an element. See this for more. Of late I came across a scenario when I wanted to click on a link depending upon the text in a text box. Herein parent of text box and parent of link were at the same location. More over there could have been many such combinations in application. Fortunately I just need to pick first such instance and Web Driver any way considers only first instance when multiple locators are found matching an element. Element in question is in following html - Here I need to click on highlighted anchor on the basis of input element (which is also highlighted in image) Herein first I need to reach div parent (class = 'left couponmainarea