Manual and Automation testing Challenges

Software Testing has a lot of challenges both in a 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 a 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. Sometimes testers may add complications in a 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 the manual as well as in automation testing. If you try all these combinations you will never ship the product ;-)

2) Misunderstanding of company processes:
Sometimes 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 do not agree with some points. For this tester also requires good communication, troubleshooting and analyzing skill.

4) Regression testing:
When a 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 in incomplete, insufficient and ad-hoc testing throughout the testing 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 the boss, tester simply focuses on task completion and not on the test coverage and quality of work. There is a 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 a 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:
Sometimes 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? The decision of automation or manual testing will need to address the pros and cons of each process.

10) The 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 the organization is rewarding testers based on a 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.

14) To cope with attrition:
Increasing salaries and benefits making many employees leave the company at very short career intervals. Management is facing hard problems to cope with attrition rate. Challenges – New testers require project training from the beginning, complex projects are difficult to understand, delay in shipping date!

These are some top software testing challenges we face daily. Project success or failure depends largely on how you address these basic issues.

For further reference and detailed solutions to these challenges refer to book “Surviving the Top Ten Challenges of Software Testing” written by William E. Perry and Randall W. Rice.

Over to you:
Many of you are working on manual and/or automation testing field. Though I have addressed many of above challenges in our previous articles, I want your views on handling these software testing challenges.  Feel free to express your views in the comment section below.

138 thoughts on “Manual and Automation testing Challenges

  1. To be frank, I do not have any knowledge of testing but want to join any Testing Institute.

    Please help me how to get a job as a tester after these many years as a BPO employee

  2. Hello friends,
    I work as a STE in an in-house product of our company and would like introduce testing metrics to measure the quality and other aspects of our product.
    I came across somewhere that not all metrics will be useful at the early stages of metrics introduction, and that different metrics can be introduced when the existing ones prove to be worthy / useless for the project, i.e., basically a trial-error method.
    I would like to know any site or blog or anywhere, where I can get the list of metrics (with their formula) that are prevailing / commonly used in the industry. I would also like to know how to interpret the result of the metrics.
    Thanking you in anticipation.

    Take Care..
    ShreeG

  3. sir i am working in small company and my designation is project tester and i am testing only php web development how to develop my skills plz help me

  4. Hi ,
    Im new to testing can anyone help me by providing me with real time testing problems and the solutions to those problems. Preferred for commercial insurance application ( insurance domain) and mortgages ( banking domain). I would really appreciate if i could get at least 4-5 problems and solutions for each domain. I would really appreciate this help given to me. Thank you

  5. Stubs and Drivers
    stubs are used in top down integartion. It simulates the activity of a lower level component.
    Drivers are used in bottom up integration which simulates the activity of a higher level component

  6. Actually what is the use of QTP? i am working as a software tester,i do with mannual testing only,i tried to study QTP,but it seems so useless

  7. hi,
    Could any one suggest me which one is best “Manual or Automation”. Currently i am in Manual Testing. Or else i want to switch over to Automation.

  8. Hello Sir,
    Thank you for the post. We have found it very useful as we have faced most of the points mentioned above in daily testing.

  9. As a manual tester I’m facing most of the challenges mentioned by you in day to day testing activity, I just wanted to share few challenges:
    1) Testing new technology/domain: My company has entered into SharePoint domain (developing Intranet sites), before switching to SharePoint I was into web application testing. so once I switched to SharePoint, initially it was a new technology & lack of experienced staff for sharepoint , as a tester I struggled a lot to get to know actually what is sharepoint testing?
    2) Inadequate requirements from stakeholders/Project managers: Few of my projects were not organized properly, as few projects doesn’t have BRS or FRS documents, Project managers/leads used to interact with clients directly & gathered the requirements with no proper document/ sometimes used to give us requirements orally. Due to this testing team had no proper document to refer & need to interact with project managers/leads on regular basis & gather requirements.

  10. Hi..Great study. I am a B.E student really it was very useful for me to gain at least some hint like knowledge… But can you please help me by making me understand how Testers will handle a complex situation I mean a bigger Manual test. Will they be using any algorithms ?? If so which is preferred EA or ACO? And Why?

    Thanks… :)

  11. Hi,
    I am in testing field for past 6 years. I am ready to give training in testing field even I can help you with the interview process and procedure. If anyone interested mail me to “aptautomationtester@gmail.com”.
    Regards,
    Guru

  12. Hello sir,
    iam pavan btech ece 2012 passed out now iam doing a job in small company as a manual tester were iam only one tester in my company doing only the functionality part testing so as a manual tester there will be no growth so now i deceided to move to automation by keeping 2+ fake experience so for that wat should i learn iam a ece student no programming knowledge so please give me suggestion that whether i should continue in this small company or i should go by keeping fake experience to other company because in my company iam only single tester there is no test lead so whether i can gain knowledge by staying in this company by only testing functionality part please tell me iam in full confusion reply to my mail sir

  13. Hello,

    I like your article.

    Apart from challenges mentioned I would like to add two more challanges which I faced.

    1. Data Assertion Criteria.How Much data will be sufficient to test is always difficult to decide.

    2. Second one is difficult to Automate the ETL testing.

    Regards

  14. Questioned that were asked in exams plz help:

    1. Which are the fallowing procedures are related to review in veloci-Q ?
    a. Proposal/ Contract review
    b. Release review
    c. Review
    d. All of the above

    2. The highlight of acceptance testing are:
    a. Check the system against requirement specification
    b. Testing done by customer and not by developer
    c. Focuses over whether the system delivers what was requested and is informed by the business
    d. All of the above

    3. Test audit observation should be captured in ____________
    a. Test audit report
    b. Test report
    c. Test observation report
    d. All of the above

    4. ___________ can be done with checklist, issues list, walkthroughs, and inspection meeting
    a. Validation
    b. Verification
    c. Inspection
    d. Testing

    5. In the table review, who records the defects and classified errors
    a. Review reader
    b. Recorder
    c. Reader
    d. Author

    6. ___________ testing should be carried out if there are multiple module in the projects
    a. Unit
    b. Build
    c. Modules
    d. Systems

    7. ___________ is used to test operation and input output data to ensure that software is performing well
    a. Review techniques
    b. Verification
    c. Software testing
    d. All the above

    8. ___________ are conducted to eliminate and find errors/defects in the early stage of development
    a. Review and testing
    b. Review
    c. Validation
    d. All of the above

    9. Why is multiple round of testing recommended
    a. Accommodate bug fixes and eliminate maximum defects
    b. Shortage of resources to complete testing in one round
    c. Set of test cases can be executed in each round
    d. For testing basic requirement, implied requirement, performance measures in various round

    10. The challenges in testing are :
    a. Lack of testing tools
    b. Often development effort increase and there is very little time for testing
    c. Generation of adequate test cases
    d. All of the above

  15. Hi,

    I like to share some of my personal difficulties here.i have 2.7 years of experience in testing.yesterday i had a interview with the client?what are all the difficulties which you face in testing?
    My answer is 1)reopening the defects again
    2)Not understand the requirements/brd is missing in our concern
    can any one agree what i said???

  16. Hi,

    I have a windows based tool which I need to automate by UFT or any other automation tool, but the problem is I am not able to identify the objects of that tool, the tool is developed in openInsight technology.
    Please help

    Thanks

  17. Great article! These are the exact challenges we are trying to overcome at Testing Algorithms, LLC. by innovating various algorithms. So far we have come up with a modelling approach that helps in reducing the impacts of point 1, 4-10 & 12. With this solution, behavior of a software application can be captured using a model, that can be automatically converted to prioritized and optimized test cases in no time. Request you all to visit http://www.testingalgorithms.com and share your feedback.

  18. Invaluable analysis ! I loved the details ! Does someone know if I might acquire a blank a form example to work with ?

  19. I need few blogs and podcasts to listen to improve the quality of my work as a Quality Engineer. Also, need training on how to train other team members to use Git and Gherkin training. Someone please help, I will highly appreciate your help.

Leave a Comment