How do you improve your testing?

Home Forums Software Testing Discussions How do you improve your testing?

Viewing 16 posts - 1 through 16 (of 16 total)
  • Author
  • #12738
    Ronan Healy

    What do you do to get better at testing? Do you attend meet-ups, workshops, watch webinars?

    Do you practice areas of testing that you usually do not utilise at work or do you do something else?

    Do you see what work colleagues are doing, discuss testing with them?

    There are a number of different ways to approach this, I’m just curious what people’s preferences are?


    Improving your testing, is about talking and thinking about live in general 😉
    This sounds quite philosophical, (although not for a Qualisopher), because if you want to improve your testing you must be willing to open your eyes and mind for every thing around you: read, listen, discuss about what drives people and organizations, participate as volunteer in non-profit organizations, learn from sport, art, literature. They have solved or have been facing problems we are facing too in IT.
    Make it your quest which will last for the rest of your live and has so many different points of view. So go for the quest of learning, understanding, investigating so you will be able to improve yourself and your work step by step, day by day, Until you die (Amen)

    the Ard of testing


    To improve testing is necessary a combination of having the correct (or improved) domain knowledge, good test plan design taking into account inputs from different perspectives (development, portfolio, clients, other testers), and continues updates and reviews during the testing. Also having more than one tester with different backgrounds would help a lot to cover more scenarios.


    What works for me is to know the Business Domain and design test cases based on that.

    So as i am writing this post, found a new word “Empathic design”.


    By constantly learning and reading up on new strategies and techniques.

    Ronan Healy

    What works for me is to know the Business Domain and design test cases based on that.

    So as i am writing this post, found a new word “Empathic design”.

    That’s a great approach to have @sasha.

    How did you decide on that approach?

    Devanathan Ram

    Actually there are a lot to do to get better in testing apart from reading blogs, watching webinars, etc.,

    Below are a few that I can think about now (also, which I did in the past),
    1. There must be many feature upgrades to the system with few updates, now the regression library needs to be refined with addition of new ones and modifications of few old ones (which I believe is the toughest task)
    2. If you have the habit of keeping track of all old Requirement Traceability matrix, the second toughest task for you is this.
    3. Presenting an end to end demo of the functionality to the business and the stakeholders once your testing team has signed off testing and handed it off to the next team or to the production. (Demos are very critical and help the business and stakeholders in many ways)

    What happens when you perform the above to task dedicatedly?
    1. You will master the product you test and there is a good probability you could move on to become an SME
    2. You create yourself a good accountability which would help you in your career forward

    These are the boundary values of testing which actually adds up a great value & quality to your testing.

    Sneha Singh

    Software testing is not a job, it’s a responsibility. Either you are doing manual testing or you are writing complex automation scripts, you are the authorized person for the quality of that particular web page / module / overall product.

    And to keep up with the responsibility in the highly competitive IT environment, it’s necessary that –

    You find something bad before someone else finds out
    You see something critical before someone else thinks about it
    You report something extraordinarily before someone else has chance to do it
    You co-relate past experiences, learning, same work experience with current task and generate a fabulous output

    Ronan Healy

    Software testing is not a job, it’s a responsibility.

    I like that quote. It’s a good way to think about your role @sneha-singh as sometimes a lot can depend on finding the bugs in software.

    Abir Khan

    1. By keeping updates from other testers from twitter, mine is : @abir11khan
    2. By following Testing communities
    3. By attending Conferences
    4. By Solving problems of others in stackoverflow and such
    5. By Practising new field like test automation.


    Currently in Global Organization, the tester can no longer work alone.

    The approach in handling just one application, versus handling one component amongst the many as 300 components interact together, is different.

    The testing community really need to learn Fast, Collaborate with each other in order to ensure the quality of the delivery.


    I have learnt the most from fellow testers. Interacting with them, understanding their way of testing. I often go through defects raised by other testers so that I know what I missed and I can take care of that in the future.

    sneha shinde

    Testing is improve when you learn and practice on testing, you should learn small things while testing.
    attending guest lectures on testing or conference.
    Doing testing class certifications.
    practice on real examples.
    this is all you are doing then your will improve.

    [commercial content removed /mod]


    @abhilashawaghm11 Please don’t attach/hyperlink commercial links inside your post / reply.


    learn software testing from good training center. zenrays technologies provide best software testing training in Bangalore


    Really nice discussion and extremely informative.

Viewing 16 posts - 1 through 16 (of 16 total)
  • You must be logged in to reply to this topic.