Posts Tagged ‘Test automation’

Software Testers are often made responsible for any bug, missed during testing or for any scenarios not tested. It’s a very common situation in most of the companies, where people work in a very tight schedule and follow Agile Model.

So, how a Software Tester can avoid these things? How one can bring the best concepts into play?

It’s all in the MIND. You don’t get much help from internet or anyone from different project, the best guide is You and Your Mind. It’s all your thinking, logical, analytic and imagination ability which will help you in the long run of your testing career.

Again, I am not talking about the SDETs who can easily get reference code from internet. I am talking about the strategy/plan, you will be following to write Test Cases, whether it’s Manual or Automation.

I believe that a Good Tester is known not by the Certificates, one has or the skill-set  one carries but by his sharp MIND. The way one creates awesome scenarios and compares the features of one’s project with existing or real time scenarios matters the most. This can help in great extent.

What are the ways to enhance your thinking, logical, analytic and imagination skills? Here are the ingredients:

1. If you are a fresher, get all the basics clear.

2. Try to adapt the technology, used in the project. If not, then try to find out the advantages and disadvantages of it. It will help you to find loop holes easily.

3. Try to indulge your in all meetings even if it’s too much technical. I can guarantee, you can relate this knowledge while testing.

4. If you are having more than 2 yrs exp, try to be expertise in one or two areas (e.g. Automation, Mobile). But I would suggest you to learn the basics of other areas as well. This will give you additional benefits.

5. Don’t only stick to testing. Pick up your interest and spend some time to know what’s going around in the world. You cannot be a tester for whole life. There are many more opportunities waiting for you.

6. Try to be happy and make others happy.

7. Have a balanced work and personal life. Don’t exhaust yourself with too much work.

8. Have a decent attitude, but if situation demands, don’t hesitate to be aggressive.

9. Be very professional with your colleagues.

10. If you are right, prove your points. If not convinced, go to heights.

11. Eat well, sleep well. Take good care of your health.

12. Take up a sport and get some time from your busy schedule to enjoy and relax your mind.

13. And last but not the least, Don’t work hard, work smart.

Please do comment in the post and let me know your thoughts.

Happy Testing …!!! 🙂


Software Testing has lot of challenges both in manual as well as in automation.Generally in manual testing scenario developers through the build to test team assuming the responsible test team or tester will pick the build and will come to ask what the build is about? This is the case in organizations not following so-called ‘processes’. Tester is the middleman between developing team and the customers, handling the pressure from both the sides. And I assume most of our readers are smart enough to handle this pressure. Aren’t you?

This is not the case always. Some times testers may add complications in testing process due to their unskilled way of working.In this post I have added most of the testing challenges created due to testing staff, developing staff, testing processes and wrong management decisions.

So here we go with the top challenges:

1) Testing the complete application: 
Is it possible? I think impossible. There are millions of test combinations. It’s not possible to test each and every combination both in manual as well as in automation testing. If you try all these combinations you will never ship the product ;-)

2) Misunderstanding of company processes:
Some times you just don’t pay proper attention what the company-defined processes are and these are for what purposes. There are some myths in testers that they should only go with company processes even these processes are not applicable for their current testing scenario. This results in incomplete and inappropriate application testing.

3) Relationship with developers:
Big challenge. Requires very skilled tester to handle this relation positively and even by completing the work in testers way. There are simply hundreds of excuses developers or testers can make when they are not agree with some points. For this tester also requiresgood communication, troubleshooting and analyzing skill.

4) Regression testing:
When project goes on expanding the regression testing work simply becomes uncontrolled. Pressure to handle the current functionality changes, previous working functionality checks and bug tracking.

5) Lack of skilled testers:
I will call this as ‘wrong management decision’ while selecting or training testers for their project task in hand. These unskilled fellows may add more chaos than simplifying the testing work. This results into incomplete, insufficient and ad-hoc testing throughout thetesting life cycle.

6) Testing always under time constraint:
Hey tester, we want to ship this product by this weekend, are you ready for completion? When this order comes from boss, tester simply focuses on task completion and not on the test coverage and quality of work. There is huge list of tasks that you need to complete within specified time. This includes writing, executing, automating and reviewing the test cases.

7) Which tests to execute first?
If you are facing the challenge stated in point no 6, then how will you take decision which test cases should be executed and with what priority? Which tests are important over others? This requires good experience to work under pressure.

8 ) Understanding the requirements:
Some times testers are responsible for communicating with customers for understanding the requirements. What if tester fails to understand the requirements? Will he be able to test the application properly? Definitely No! Testers require good listening and understanding capabilities.

9) Automation testing:
Many sub challenges – Should automate the testing work? Till what level automation should be done? Do you have sufficient and skilled resources for automation? Is time permissible for automating the test cases? Decision of automation or manual testing will need to address the pros and cons of each process.

10) Decision to stop the testing:
When to stop testing? Very difficult decision. Requires core judgment of testing processes and importance of each process. Also requires ‘on the fly’ decision ability.

11) One test team under multiple projects:
Challenging to keep track of each task. Communication challenges. Many times results in failure of one or both the projects.

12) Reuse of Test scripts:
Application development methods are changing rapidly, making it difficult to manage the test tools and test scripts. Test script migration or reuse is very essential but difficult task.

13) Testers focusing on finding easy bugs:
If organization is rewarding testers based on number of bugs (very bad approach to judge testers performance) then some testers only concentrate on finding easy bugs those don’t require deep understanding and testing. A hard or subtle bug remains unnoticed in such testing approach.