Pitfalls of Automated and Manual Testing

TestFortExpert by TestFortExpert on 03/14/2014

Pitfalls of Automated and Manual Testing

automated and manual testingSoftware testing has certain pitfalls and challenges, notwithstanding if its manual or automated one. Typically in manual testing scheme, developers via the build to test team suppose that the responsible tester or test team will select the build and come with questions about it. Testers serve as mediators between developing team and the clients; as usual they suffer from pressure from both sides of the process. Thus, it happens that testing and developing team bring on several testing problems and challenges and make wrong decisions.

Let’s make an overview of the most common and vital challenges:

1. Testing of the entire application:

It is not much possible, I think. As there are tons of test combinations and if you are willing to test all of them, both in manual and automated testing, than you will never deliver a product.

2. Not understanding clearly the company processes:

It happens that testers misunderstand the inner processes of the company or don’t understand what they are aimed for. But there are several beliefs that testers should follow with company processes only even if they seem inappropriate for current testing scenario. It results in wrong application testing.

3. Attitude to developers:

It is a big issue as it demands good communication and analyzing skills and strong will to manage positive relation with developers.

4. Uncontrolled regression testing:

Sometimes a project can widen and regression testing work goes out of control.

Pressure to handle the current functionality changes, previous working functionality checks and bug tracking.

5. Lack of skilled testers:

It is possible that bad-skilled testers would rather cause problem than ease the testing work. It can be due to bad management. This may turn into incomplete and insufficient testing throughout the testing life cycle.

6. Restraint testing:

When tester is rushed to deliver the product and asked to finish completion asap, it is never a good idea, as after that requirement 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. Where to start?

It is a good question which tests to implement first.

How to decide which tests are important over others? This requires good experience to work under pressure.

8. Understanding the requirements:

Testers need to understand the requirements given by customers through communication with them. It is their responsibility to comprehend the customers’ demands.

Any misunderstanding might lead to inappropriate testing. Testers need to have good listening and understanding skills.

9. Automation testing:

Many challenging questions can appear while doing automation testing such as if it should be implemented or if there are enough of skills and resources for automation, or if it is a good time for automated testing. You need to think through all the pros and cons of each testing and make a decision based on it.

10. When and if to finish testing:

It is a tricky question if to stop testing or not. Testing processes and importance of each process should be reviewed. ‘On the fly’ decision ability is as well required.

11. One test team and many projects:

It is a bit difficult to spread your time, energy and skills on many tasks simultaneously. It is quite impossible to kill two birds with one stone. Thus trying to manage two or more projects at the same time might result in a failure.

12. Second use of former test scripts:

Methods of application development always in a continuous change, resulting in impossibility to operate test tools and scripts. Test script migration or second use is very vital and significant but difficult task.

13. Focusing on finding simple bugs:

If you encourage testers to find as many bugs as possible and appeal to them to concentrate on a number rather on a quality it is quite a bad approach. As a result they would focus on finding easy and simple bugs rather than look for deep or hard bugs. Of course it may eventually lead to malfunctioning of your testing product as it would have major bugs unfixed, so testers would have to start all over again.

14. Dealing with exhaustion:

Increasing salaries and benefits making many employees leave the company at very short career intervals. Managements are 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!

The success of your project depends on how you treat the mentioned-above issues.

We use cookies to ensure your best experience. By continuing to browse this site, you accept the use of cookies and "third-party" cookies. For more information or to refuse consent to some cookies, please see our Privacy Policy and Cookie Policy