Cutting Testing Time

It is very often that software development projects fall behind the intended schedule. This can happen due to several reasons. Whatever the reasons are, this situation causes development time to be extended. In this case and in order to meet software delivery date, usually testing time becomes the victim. Project Management or even management ask testing team to reduce testing time (or in some cases to work extra hours) in order to meet the planned delivery date. This is one of the cases I have faced as a test lead and I want to share with you. (more…)

Testing Quote of the Week 24

“Testing by itself does not improve software quality. Test results are an indicator of quality, but in and of themselves, they do not improve it. Trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often. What you eat before you step onto the scale determines how much you will weigh, and the software development techniques you use determine how many errors testing will find. If you want to lose weight, do not buy a new scale; change your diet. If you want to improve your software, do not test more, develop better.”

~ Code Complete –  Steve McConnell

Skipping Test Plan!

One of the weird cases I encountered in my experience as a test lead is the request to skip the test plan. In this post, we will look at the test plan and the need for it from my own point of view and experience as a test lead. (more…)

Testing Quote of the Week 23

“Beware of bugs in the above code; I have only proved it correct, not tried it.” ~ Donald E. Knuth

Test Environment

Test environment is essential for testing team in order for tests to be accurate. Usually, software works well on developers machines. However the same software fails soon after installing it on customer environment. Having a dedicated test environment helps a lot in finding such kind of issues and fixing them before delivering software to the customer. (more…)