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

How can you save resources when instantiaing driver?

I asked on my previous post about what was wrong in instantiating driver on set up method? And here is the solution video on my YouTube channel (After 5 years of gap I finally added new video tutorial :)) The solution described on video tutorial uses following set up - public class BaseClassOnDemandDriverSetup { private WebDriver driver ; @BeforeMethod public void setupTest () { // Any other set up goes here } @AfterMethod public void teardown () { if ( driver != null ) { driver .quit() ; } } public WebDriver getDriver () { if ( driver == null ) { WebDriverManager. chromedriver ().setup() ; driver = new ChromeDriver() ; } return driver ; } }

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