Testing and its challanges

An activity that aimed to evaluating the capability of software or system or a program and determining that it meets its required result, is  Software Testing.

Regular testing must ensure that the  software is adequately functional. The quality of software is directly linked to the amount of testing we do. In the open source world, many users tend to work as testers, their curiosity and inquisitiveness makes the software bug free and increases the lucidity. Basically, there are two ways of testing: Automation testing and Manual testing.

Manual and Automation testing are important in it’s own place. Before any automated testing, one round of manual testing is recommended to filter out the basic bugs. More over Manual Testing is followed in more places in this industry.

Tester is the middleman between developers and the customers.  As a tester, we have some challenges, both in manual and automation.

The top challenges are:

1) Testing the complete application: Testing is a never ending process.

2) Misunderstanding  company processes: Some times, we don’t pay proper attention what the company-defined processes are and these are for what purposes.

3) Relationship with developers: There are simply hundreds of excuses developers or testers can make when they are not agree with some points.

4) Regression testing: When project goes on expanding the regression testing work simply becomes uncontrolled.

5) Lack of skilled testers: This results into incomplete, insufficient and ad-hoc testing throughout the testing life cycle.

6) Testing always under time constraint: There is always time crunch and in the initial process we cannot decide which testing we should adopt: Manual or Automation.

7) Which tests to execute first: which test cases should be executed and with what priority?

Understanding the requirements: Normally, tester fails to understand the requirements.

9) Decision to stop the testing: Some times it is difficult to decide when to stop testing.

10) Testers focusing on finding easy bugs: A hard or subtle bug remains unnoticed in such testing approach.

Last but not least, project success or failure largely depends on how you address these basic issues. The purpose of testing should be quality assurance, verification and validation or reliability.