Skip to main content

What when your employer kills software testing job?



Screenshot from 2016-07-27 14:58:21.png


Few months ago I faced a situation wherein my employer decided to stop having software testing job. Development teams were tasked to carry out QA /Testing activities along with development tasks. Only time would tell how successful or disastrous it turns out to be but my QA colleagues and I were faced with difficult times especially when many of us were in a foreign country. Test automation engineers were given the option to switch to development but I decided to not switch. I decided to continue with in the field of software testing which eventually resulted in me finding a new job. Here are my thoughts on what you can do if you also face this situation when your software testing job is killed -


  • Knowledge transfer to development team. Devs are usually lazy when it comes to integration/system testing (If not then probably we would have never had software testing field) or they don’t have enough information about all the pieces of system put together. You would do great favour to them to share system and testing knowledge with them so that they can continue with testing in your absence.


  • Look for short term testing opportunities within your current employer. Sounds contradictory when your employer does not want to have software tester at all? If you work in an MNCs then chances are that subject matter experts would be required by few teams. Soon after I was told that I should switch to development I was contacted by one team to help them on performance testing. They had been trying to hire performance testing expert but did not any have success. This was one opportunity I could not say No to. I had worked on performance testing in past but was far away from being a subject matter expert. In jumped in to new task, got to work on performance testing (exclusively) for six months. Lots of learning and interesting results. If I had said no to this opportunity then I would not have been able to learn about performance testing what I know today. If you want to know more about my performance testing learning then you can follow Performance Testing videos


  • Don’t switch to another role for sake of it. Don’t take on development or any other role your heart is not ready to work with. Never let one company decide about the field you should work on. Follow your heart and work on what you want to work on. If you take up an unwanted role under pressure then you would end up doing shoddy job anyways. Would it be worth it?


  • Last but not the least, gear up to find a new job. In fact be ready to find a new job any time in your career. There are no permanent jobs in IT industry but there are many companies on lookout for software tester. This is what I did and found a new job in the fields of software testing. I am not a developer and can not let someone else decide what I want to work on (full stop)

Have you ever faced such situation? What did you do? Or what would you do when you face such situation in future?

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

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

XPath and single quotes

I had tough time dealing with XPath and single quote. Though W3C recommends using ' to escape it but I never got it working, let me know if any of you get through. Came across this blog and found that “concat” could be used in this situation. So original XPath expression is – //meta[@name=’DESCRIPTION’][@content=’Tester’s Test’] This is some thing which certainly fails as single quote in “Tester’s” marks it at end of string and then XPath blows up, next trial was – //meta[@name=’DESCRIPTION’][@content=’Tester''s Test’] This does not work despite w3c recommendation! And then I used concat function and split the string as – concat(‘Tester’,”’”,’s Test’) NOTICE that single quote is kept in double quote while other characters are kept in single quotes. So XPath looks as – //meta[@name=’DESCRIPTION’][@content=concat(‘Tester’,”’”,’s Test’)] And this works charm.