Skip to main content

Software Testing - What keeps you engaged or disengaged

So were you always determined to be software tester (tester by choice) or happened to be (tester by chance). And none of this is better than other. Tester by chance might be as skilled at software testing as tester by choice.
But the question is what keeps them going, what keeps them engaged in work and some times despite having tested same features time and again. So if you were to list out those pointers what would you say, or better if you had to list what keeps you uninterested (which might be an easy question). So let me list down what might disengage a tester from work -

  1. Project is utter crap. None or least (read as none) value is given to testing team, leaving testing aside.
  2. Testing team is more interested in blaming each other of not finding a defect than adding any value to team.
  3. Your salary is least and you had worst appraisal discussion of your life.
  4. So your team members or members in other team are working on test automation. They are using QTP, Selenium and you... well no chance what so ever. And you think automation will bring you to the level of development team (Could write a blog on this nonsense topic it self)....
  5. Your project manager wants you to test any time and every time. 24/7 testing is the dogma s/he is born with. You are a tester and this makes you liable for testing... forever.
  6. How dare you ask about requirement documents? and how dare you missed that production defect !@#!@#!@#$%#$
  7. So your friend is on extended onsite trip and you, well not even sent for visa stamping till now
  8. You attend all the meetings for project and work, WHERE IS THE TIME FOR TESTING
  9. and 1000 situations you would have faced......... Could you list a few, and those enthusiasts who could list otherwise also....
For me its the team which matters lots over any thing else. Once happened to work on worse project having every possible difficulty but team dedication kept me going every time I was worn out. I wish every tester gets to work with such great team at least once in their life time....

Comments

  1. Hi Tarun,
    I do strongly agree with your forceful bullet points and the notion about the team...
    Kudos!!!!

    ReplyDelete

Post a Comment

No spam only genuine comments :)

Popular posts from this blog

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

Verify email confirmation using Selenium

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

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