Skip to main content

2012 - Software Testing Trends

Don't be taken aback if you see following changes in software testing (read people perception) in 2012 -

Management's Disillusionments
  • Tester != Bots
  • Testing != Monkeying around
  • Tester != Project delivery blockers
  • More tester != More defect discoveries
  • Testing != Just keep testing
  • More tester != Less time needed for testing
  • Automation tool != Less manual testing needed != Less testers needed
  • Tester salary = Dev salary (sigh)
  • Testing certificate != Expertise
  • Automated tester !> Manual tester (though vice versa may be true)
  • Production bug != Only testers are responsible
  • Night out != More work done
  • Automated testing != Manual testing
  • Testing != Only testers' job
  • Missed deadline != Reduce testing time
  • Heavy project metrics !=  Confident testing
Tester's Disillusionments
  • Programming knowledge != Exclusive to developer
  • Automation tool knowledge != Better salary
  • Tool expert != Better testing
  • Dev != Enemy
  • Commercial tools !> Open source/Free tools
  • Proximity with Dev = Better grasp on project = win win
  • Automated testing !> Manual testing
  • Test certificate = waste of money = serious waste of time = Heinous crime
  • Community participation = Increased expertise
  • Exploratory testing != Adhoc testing
  • Onsite != More money
  • Tester's Job != Only manual testing
Do you see any more trends coming up?

Comments

Popular posts from this blog

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

Verify email confirmation using Selenium

Email confirmation seems to be integral part of any registration process. I came across an application which lets you provide your email address. You can follow the sign up link in you mail and then complete the registration process. Lets consider we provide GMail address for it. Now if were to use only Selenium then we would have to follow following steps - Launch GMail using Selenium; Some how search for new mail in the list of available mails; Some how click on it; Parse the mail message; Get the registration link; Follow up with registration process What do you think of an approach in which you can

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