Entries tagged as Manual Testing
What is a bug?
Bug can be defined as the abnormal behavior of the software. No software exists without a bug. The elimination of bugs from the software depends upon the efficiency oftesting done on the software. A bug is a specific concern about the quality of the Application under Test (AUT).
Read More...
Project isn’t big enough to justify extensive testing
What if the project isn’t big enough to justify extensive testing?
Consider the impact of project errors, not the size of the project. However, if extensive testing is still not justified, risk analysis is again needed and the same considerations as described previously in ‘What if there isn’t enough time for thorough testing?’ apply. The tester Read More...
If requirements are changing continuously
What can be done if requirements are changing continuously?
A common problem and a major headache.
- Work with the project’s stakeholders early on to understand how requirements might change so that alternate test plans and strategies can be worked out in advance, if possible.
- It’s helpful if the application’s initial design allows for some adaptability so Read More...
Isn’t enough time for thorough testing
What if there isn’t enough time for thorough testing?
Use risk analysis to determine where testing should be focused. Since it’s rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgment Read More...