Why Software Testing Needs Revolution? (and Here is How)

Like every technology, software testing is also growing. As we see, nowadays, technology is evolving fast, there is a question to ask ourselves โ€“ as a Tester are we growing? (Do not misunderstand this question as growing by learning 5-6 automation tools).

After spending almost a decade in the industry and observing the number of projects and technologies, I would like to claim that this is the right time for Software Testing to be revolutionized.

As usual, I have points to support my claim. Read on –

Why Software Testing Needs Revolution

End-users Viewpoint Has Changed

End-users and customers are spoiled for better with multiple choices. Due to neck cutting competition, every business holder wants to have maximum customers and to attract customers or to satisfy end users, they are ready to hit any milestone, be it a timeline, cost, the product itselfโ€ฆ..anything.

And with this change, customers and end-users want more perfect, more aesthetic, more reliable products or applications in a defined timeline. Also, customers nowadays do not provide vague requirements and as they are very clear about the requirements they do not want to do any compromise when their requirements are implemented.

With this scenario, as a Software Tester, we cannot just keep doing traditional testing. We too need to change ourselves, our thinking process, our ideas, our way of working and our eyes to observe.

Here is how:

  • Canโ€™t we ask more questions when we read requirements?
  • Canโ€™t we prepare brief documentation for our and teamโ€™s understanding?
  • Canโ€™t we work on improving communication?
  • Canโ€™t we ameliorate our analysis and reporting skills?

If the answers are yes, what are we waiting for? This is the right time to implement, execute, change, observe and report.

Technology Is Changing Rapidly

Changing Technology

When mobiles were less popular and people were rarely talking about mobile application and most of the people did not think about using different applications on the move, life was easy. Wasnโ€™t it? With the growing market for mobile applications, the definition of Software Testing has been changed.

Mobile Testing is totally different than Traditional Testing and we have to get used to it.

Here is how:

  • We need to think about more scenarios
  • We need to observe more people and how they use their mobile
  • We need to understand the ultimate purpose of product/application

Again, if you are agreed, what are we waiting for? Letโ€™s start implementing this moment.

Numerous Tools But Lack Of Ideas

automation must be coupled with manual

Automation is in demand and the most painful fact is โ€“ people think that if they know automation, they will be automatically considered as a good tester.

Sorry to say, but thatโ€™s not the case. No tool can replace the human mind. Yes, tools definitely make our life easier but ultimately they are created by humans and they need human efforts to use.

I am not trying to say that manual tester is better than automation one or vice-a-versa but the point here is testing cannot be completed without ideas and manual efforts. No tool can test/report application/productโ€™s behavior on its own. The tool only follows the script and you need to be prepared to analyze the results generated by the tool.

Nowadays, when the market is presenting 100s of new tools and utilities and when we are always at short of time for testing, automation is a must requirement but it should be coupled with manual testing.

Here is how:

  • Letโ€™s learn something new every day and implement it
  • Letโ€™s think about 5 new ways you can test the current application/product
  • Letโ€™s do some detailed research about which tool can make our life really easy
  • Letโ€™s observe the product more closely and provide more details about the bug

Certification

Software testing Certifications

How many of you would agree to this statement – anyone can learn and explore more if he is not under pressure of exam? After years, we can understand that those races for marks took us nowhere. Instead, we would have taught the subject just to learn.

(On a lighter note, my husband always makes the remark that whenever I have guests invited for dinner, I unconsciously add more/less salt as I feel the pressure. I am sure, in one or the other area of life, we all observe that kind of pressure situation where we have to perform within limited time and believe me, that fear of performing well makes us so conscious that we forget about learning and enjoying, i.e. the process. We just become result-oriented and thatโ€™s not a good sign for the community).

I am not opposing certification but they are not at all measurements of your real skills. No exam can assess the capabilities of someone within the time limit. When it comes to Software Testing, itโ€™s about growing day by day.

  • You cannot think 1000s of ideas in a day,
  • You cannot learn an automation tool in hours,
  • You cannot observe 100s of bugs within the first week of testing,
  • You cannot communicate well with developers and customers from the starting point of your career

But it surely is a matter of growing. With experience, we learn, implement, nurture our skills and develop ourselves. Learn from your past mistakes and keep notes of them. When working on other projects, remember those mistakes and try to not repeat them.

The Tendency To Not Upgrade After Reaching A Position

Keep on testing

Itโ€™s ok if a senior developer turned lead/manager does not code but a real test manager always tests. Yes, when you want to forget the basic skills, you are screwing up your career. No matter, how many years of experience you carry, keep your brain working the way you did. Spend at least a couple of hours for testing.

Here is how:

  • Test Real-time products
  • Suggest ideas to make the product more useful
  • Study the market and learn why some products are bestselling and others are not.
  • Understand how ideas are being implemented in different ways

Conclusion

Ultimately, as I have been writing for the number of times here, software testing is all about ideas. No software tester can survive in the industry if he is not a good idea generator. So make your mind work. Co-relate your product with any real-time product and think about how you would test it. It will give you a new sight to look at.

Also, do not forget to add weapons of reporting and communication in your testing beg. The person who cannot communicate well, cannot achieve success in any industry. Equip yourself with training and implement learning to report better and to communicate fruitfully.

About the author: This awesome revolutionary post is written by STH team member Bhumika Mehta. She is a project lead, carrying 7+ years of software testing experience. She is totally into testing and loves to test everything that exists.

As usual, waiting for your commentsโ€ฆ..letโ€™s make a revolution together.

Happy Testing ๐Ÿ™‚

Recommended Reading

26 thoughts on “Why Software Testing Needs Revolution? (and Here is How)”

  1. great post. thanks for valuable suggestions and helping this testing field to be on top.

    Reply
  2. Well explained especially the example of Salt and Guest. Very true. Awesome post

    Reply
  3. Good post, with nice information.along with example.
    Thanks for this… ๐Ÿ™‚

    Reply
  4. Really it’s true we software testers need to evolve…

    Reply
  5. @Sheetal, @Vamsi, @Kiran, @Ahmed,

    Thanks for encouraging words and glad to know that you liked the post. Stay tuned for more information ๐Ÿ™‚

    Reply
  6. hi Bhumika,

    this is really nice post for revolution.
    i also agree with you all points that testing need revolution .
    i am happy that my thinking about traditional testing in mobile is correct. Now i have proof of your post with that “WHY software testing need revolution ?”

    Thanks for this post…!!!

    Reply
  7. This is correct, nice article software testing is all about ideas and we have to be moving around it

    Reply
  8. Hi Bhumika,
    — Once again, excellent work. We appreciate your notion.
    — The 4 points (questioning the requirement, documentation, imp communication, reporting QA tasks precisely) u mentioned carries a lot of meaning, if anyone wants to move ahead in the industry.
    — Want to add one more thing, never read the Requirement Doc like a paragraph. Read the doc and prepare a dummy wireframe of ur understanding.
    Try to relate with real world applications. This will surely inflate ur vision about the product and hence u will come up with more questionable scenarios right at the requirement stage.
    — A request, keep sharing ur thoughts.

    Vijay N.

    Reply
  9. Great, keep it up!

    Reply
  10. Hello Bhumika as usual your post is always inspiring and it forces you to think differently. You hit all the points that need to be revolutionized in QA industry , thanks for sharing such a valuable information keep it up… !

    Reply
  11. Hi Bharat and Vijay N.,

    Thanks a lot for those kind words….I am really inspired by them ๐Ÿ™‚

    Reply
  12. @Vijay & @Bhumika:- I am agree with your points and the way u have presented your ideas,its definitely going to make a print on mind but few concerns always confuse mind which are:
    1.Most of the time i hear if you are good in automation your career will fly.Why?(If you know QTP you would be considered on upper hand while filtering resume)

    2. If you have cleared ISTQB certification you would be considered on upper hand.Why? (As any certification can not define your idea generator level)
    There are so many companies those does not work the way we think or standard what has been defined in books or better you can say general standards

    As an example i would like to say in our books or websites it has said prepare this after this(STLC & SDLC) but it does not happen in real.

    Reply
  13. @Reegan,

    First of all thanks for reading the post and agreeing with some point. Answers to your concerns :
    1. there are two things here – knowing the tool and working on the tool. Knowing any tool will not impact on your career positively until you do not know how to analyze the data and what to automation and what kind of logic to be applied. So, it might be true that for SOME companies, your CV will be given priority while filtering but in long way it will not work as you need to show relevant skills too. The side note is – logically if you know any tool, it will restrict your vision as you think you can do anything with that tool and this will stop you by learning new things. How many of automation testers know RFT and QTP both? Why people are not interested in learning JMeter if they know silk performer?
    2. I simply disagree with the point that any certification will be able to make positive impact. Certifications are basically to check your fundamental knowledge about software testing. And as I said earlier, software testing is all about ideas and so no certification will be able to check your testing capabilities.
    3. No company can fully follow the theories in books. In practical world, there are many constraints and so we have to do compromise while following the general processes. Everyone adapts what is suitable and I would say, until quality of product is not impacted there is less concern about whether you followed agile or waterfall or whether you documented test plan or not.

    I hope I attended your concerns correctly.

    Reply
  14. Revolution implies there is something to rebel against and something new to move to. In many ways some of us (testers) have preached against bad testing for years. So yes, we need to rebel against bad testing, which is very common. But what Bhumika Mehta is talking about, is more evolutionary for those newer to testing than revolutionary. Certification of knowledge does not make one a skilled tester. To be skilled, we need to practice, practice, practice. We’ve known this for a while in most fields of work.

    Reply
  15. Your article is very inspiring. There is no other way you can tell it is always to good to grow in the right direction.
    I am looking for jobs and I will definitely make this a habit.

    Reply
  16. Great article. I agree that software testers need to help influence and change how testing is viewed and focus on bringing value added services to the table.

    Reply
  17. Excellent article! I completely agreed that Software testing is all about ideas. Thanks for sharing your thoughts.

    Reply
  18. must say…a very revolutionary & innovative article…thanx…

    Reply
  19. @SS, @Prajakta, @Anand

    Thanks a lot for your readership and glad to know that you liked the article.

    Reply
  20. Nice article….very inspiring…

    Reply
  21. Nice article. I loved it so much that I have even shared with my colleagues …inclusive of Dev as well ๐Ÿ˜€

    Reply
  22. Nice Article. Just wondering on a question keep running on my mind.

    What is the future role of a software tester ?
    Where a tester with 15-20 years of testing experience fits in the current or future markets ?

    Reply
  23. Thanks Bhumika for answers!!
    Yes,You may right for point 3–> No company can fully….but my point where i have doubt yet,why you need to go through those books(As company adapts and implements process as per their convenience) as well if you want to clear certificates.

    Very True:-
    The side note is โ€“ logically if you know any tool, it will restrict your vision as you think you can do anything with that tool and this will stop you by learning new things.

    Yes,and a perception for same what i have A person must be knowing what all he/she knows about tool and what all he/she can execute very quickly and a point where he/she lacking

    Reply
  24. it’s been 6 months since i have been in this industry… i had stereotype mind of learnt evrything..i was rejoicing my QA life.. your post opened my blind folded eyes..finally its time for me to wake up and be updated… will be waiting to hear more from you..thanks a lot for your post..

    Reply
  25. It’s very nicely laid out basic assets for a good tester. I agree that testing is not about executing the test cases, but more about thinking through scenarios and cutting through logic complexity to get most efficacy in test case design and strategy seeking.

    Learning by doing it is a way to grow. Thinking deeply when you learning plays a more important role to make you a great tester!

    Reply
  26. @Yogeshwar.n

    I am glad that the post was on time to open your eyes and wake up to the new opportunity to learn ๐Ÿ™‚

    @Frank.Qu

    Thanks a lot for stopping by and commenting.

    Reply

Leave a Comment