Most 14 challenges@testing

4
Testing Challenges by Subbu: 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: 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 are not agree with some points. For this tester also requires good, 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 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 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: 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.

Transcript of Most 14 challenges@testing

Page 1: Most  14 challenges@testing

Testing Challenges by Subbu:

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:

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 are not agree

with some points. For this tester also requires good, 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 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 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:

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?

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.

Page 2: Most  14 challenges@testing

Testing Challenges by Subbu:

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.

14) To cope with attrition: (of a person) deal effectively with something difficult.

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!

Sometimes Tester needs common sense to test an application!!!

I am saying this because most of the times it is not possible to test the whole application within the specified time. In such situations it’s better to find out the risk factors in the projects and concentrate on them.Here are some points to be considered when you are in such a situation:

1) Find out Important functionality is your project?

2) Find out High-risk module of the project?

3) Which functionality is most visible to the user?

4) Which functionality has the largest safety impact?

5) Which functionality has the largest financial impact on users?

6) Which aspects of the application are most important to the customer?

7) Which parts of the code are most complex, and thus most subject to errors?

8) Which parts of the application were developed in rush or panic mode?

9) What do the developers think are the highest-risk aspects of the application?

10) What kinds of problems would cause the worst publicity?

11) What kinds of problems would cause the most customer service complaints?

12) What kinds of tests could easily cover multiple functionalities?

Page 3: Most  14 challenges@testing

Testing Challenges by Subbu:

How to Improve Tester Performance?Many Companies don’t have resources or can’t afford to hire the required number of testers on the project. So

what could be the solution in this case?

The answer is simple. Companies will prefer to have skilled testers instead of an army of testers!

So how can build skilled testers on any project?

1) You can improve tester’s performance by assigning him/her to the single project.

Due to this the tester will get the detail knowledge of the project domain, Can concentrate well on that

project, can do the R&D (Research and Development) work during the early development phase of the

project.

This not only builds his/her functional testing knowledge but also the project Domain knowledge.

Company can use following methods to improve the Testers performance:

1) Assign one tester to one project for long duration or to the entire project. Doing this will build testers

domain knowledge, He /She can write better test cases, Can cover most of the test cases, and eventually can

find the problem faster.

2) Most of the testers can do the functional testing, BV (Boundary value) analysis but they may not know how

to measure test coverage, How to test a complete application, How to perform load testing. Company can

provide the training to their employees in those areas.

3) Involve them in all the project meetings, discussions, project design so that they can understand the

project well and can write the test cases well.

4) Encourage them to do the extra activities other than the regular testing activities. Such activities can

include Inter team talk on their project experience, Different exploratory talks on project topics.