Testing Posts

Quality of Testing Vs. Quantity of Testing

Quality of Testing Vs. Quantity of Testing

A lesson I learned from working in many projects as a tester or testing team leader is to focus on the quality of testing rather than the quantity of testing. It is a big mistake to measure testing effort and whether testing is good or bad by looking only to the number of test cases, number of issues found, number of testing hours or number of testers. (more…)

Reducing Testing Time and Blaming Testers

Reducing Testing Time and Blaming Testers

Even though testing time needed for any software development project is agreed on at the beginning, it is common that management team decides to reduce testing time in case the project falls behind the schedule. Management team aims to bring the project back on schedule in order to release the software to customer(s) on time and avoid any penalties as a result of the delay. This case is very common. However, I wonder why reducing testing time is usually the preferred option to bring the project back on schedule? (more…)

One Way to Improve Your Testing Skills

One Way to Improve Your Testing Skills

There are many testers who look forward to improve their testing skills. They do their best to attend different trainings in testing field. In trainings, those testers will meet the trainer who has experience in the topic in addition to other participants looking forward to gain knowledge and improve. (more…)

Why don’t Developers Test?

Several times and when I get to see some output from the development team, I do ask myself: What if developers have tested their work well? Unfortunately, the majority of developers stop when they get the job done with development only. They do not walk the extra mile and do testing. If they do testing of their own work, then many software issues would have been solved early which means less time, effort and costs for the project. The question is: why don’t developers test? (more…)

When Testers Lead

When Testers Lead

Usually and during the lifetime of any software development project, programmers do take the lead and control almost all project activities. They keep their focus and goal to finish the tasks especially writing the code in addition to to get it running. Programmers are always in a rush especially when they follow Agile methodology. This rush causes them to ignore testing of their code including both unit testing and integration testing. Also and once you ask programmers about testing or why they ignore testing then you will find out that they consider testing  as a destructive activity and will waste their time. In addition, programmers do believe that testing team should find all the issues in the software including issues with the code. Unfortunately, not only programmers think like that. You may find some senior employees or even those in management level who share the same thoughts. However, what if the opposite thing happens? What if testing team takes the lead? (more…)