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?

Labels:

Comments

Post a Comment

No spam only genuine comments :)

Popular posts from this blog

Distributed Load Testing with JMeter

Distributed Testing with JMeter When one JMeter client is not able to offer amount of threads required for load testing then distributed testing is used. In distributed testing - One instance of JMeter client can control number of JMeter instances and collect data from them Test plan does not need to be copied to each server, the client sends it to all servers note - JMeter will run all the threads on all the servers, hence 100 threads on 5 JMeter server would pump 500 threads in total. If many server instances are used, the client JMeter can become overloaded and so the client network connection. This has been improved in latest versions of JMeter by switching to Stripped modes, but you should always check that your client is not overloaded When Client (master) and Server (slave) nodes are on same network (no SSH required) Configure Client Node Herein client is referred as the machine controlling test execution on other JMeter nodes. This is also referred
Read more

Appium and android mobile app automation

Next appium and Android mobile app automation video tutoria l is live. If you are new to appium then please check - appium-tutorial This video tutorial covers - Start vysor (Just for this session and not mobile automation :)) Start appium and start appium inspector Desired Capabilities platformName - Android deviceName - L2N0219828001013 (as seen on "adb devices") Saved Capability Sets Start Session Scan app elements using appium inspector Get appPackage and appActivity using "APK info" app Install "APK info" app and open app whose appPackage and appActivity are required i.e. calculator Check top section of app icon com.android.calculator2 is app package com.android.calculator2.Calculator is app activity testng.xml file settings for running Android app tests Test details com.seleniumtests.tests.mobile.AndroidAppTest and CalculatorScreen class View beautiful STF test report  
Post a Comment
Read more

Using chrome console to test xPath and css selectors

Note: If you are new to java and selenium then start with selenium java training videos .       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 wri
Read more