Here are the possible solutions to common problems that you may face during your work as a software tester. These tips are based on my discussions with hundreds of software testers over the last several years.


Tips to handle

Hectic schedule due to unforeseen delays, parallel projects or resource constraints

Plan your testing tasks assigning them priority according to their value or urgency.Execute these tasks from highest priority downwards.Many a time, it is not possible to get more time and it makes sense to stay calm, accept the need of the extra effort needed and put that effort in.

Inadequate knowledge (technical or functional)

In the long-term, one has to build the required knowledge in order to perform well. Until that time, one should use all the available resources to get rid of this handicap. Useful sources of help are colleagues possessing the required knowledge, project documentation and the wealth of information available on the web (e.g. product literature, FAQs, forums, blogs and so on).

Poor or incomplete requirements

The tests one executes should cover each requirement. Discussions with business analysts/ system analysts/ developers/ support personnel/ other testers, prior project requirements, design documents, comparison with prior application and similar applications are just some of the sources one can use to get a solid handle on the entire requirement set.

A problem with other teams e.g. development

Such a problem is highly specific to the particular situation. It is often useful to first understand where the other person is coming from, solicit help from one's seniors or managers and try to resolve the situation prudently before it becomes big.

Adhoc test process or re-work

Any process has certain inputs, certain steps and certain outputs. In order to minimize own re-work, review each input (e.g. functional requirements, test case format, available test data) before accepting it, perform each
task carefully (informing your manager/ client and the people downstream about the progress) and help each output get accepted by the stakeholders (e.g. development team, management and release team). Other than this, it is often useful to "be in the know" regarding the developing situations in the project in order to prepare for them ahead of time and avoid work which would need to be repeated.

Related Documents
  1. Manual Testing (1533)
  2. Software Tesitng Overview : Manual Testing (1546)
  3. Seven steps of Manual Testing (1750)
  4. Test Plan Template (2652)
  5. 123 of software Testing : An Introduction into Software Testing) (2854)
  6. Software Testing Resources from a1qa (1393)
  7. Software Testing Fundamentals봀oncepts, Roles, and Terminology (1633)
  8. Software Testing : Overview in India (1281)
  9. Software Testing & Quality Assurance FAQ (1695)
  10. Software Development Life Cycle (1980)
  11. Philosophy and Software Testing (1620)
  12. Testing interview question (1682)
  13. Developers Don셳 Like Testers, Because They Don셳 Know How to Use Them (1471)
  14. Evaluation of software reliability (1899)
  15. Essential Software Testing Tools Blog (1223)
  16. 6 Basic Criteria For Testing Requirements (1648)
  17. Myths and Rakes: the Purpose of Testing is to Find Errors (1526)
  18. Software Tesitng whitepapers from crestech (1091)
  19. 2011-11-07, Conference on Testing Software and Systems (ICTSS'11) @ France (2241)
  20. The basic definitions of automated software testing (1439)

Written by


Testing executive