QA City

Most Popular

Software Testing: Blunders to Avoid

By SiliconIndia   |     |    1 Comments
Print Email

Bangalore: With software defects and bugs being widespread and unprecedented, Software Testing today is a major component in the software development life cycle to ensure that the application is free from any defects before it can be released. Although testing is a never ending process which needs to be carried throughout the development process, however; many software testing firms still make some mistakes during the testing phase.

Arun Kumar Singh, Vice President and Global Testing Head – Sales & Marketing at Wipro in an interview with Srinivasan Viswanathan highlighted some of the common mistake in Software Testing.

1.    No Dedicated/Professional Tester
According to Arun Kumar Singh, many software testing firms lack a dedicated software tester. In such firms, testing is either done by developers or by business analysts. With a tight testing deadline, developers will rush through the testing process and overlook “semantic or syntactic bugs” as such bugs can only be detected by a professional tester. Thus, it is important to have a dedicated team of professional testers in the organization.

2.    Inadequate time for testing
Arun Kumar Singh feels that delays in the upstream phases such as the design or implementation phase results in a shortened timeframe for testing. Thus, in order to meet the testing deadline, testers rush through the process and this result in buggy software. Singh highlighted the need to give sufficient time for testing and advised testing firms to re-plan the product’s release when a project is delayed.

3.    Start testing after coding and UT (Unit Testing) is completed
According to Singh, in order to reduce 20 to 30 per cent defects in an application, testers should begin testing the application once there is a requirement. The agile methodology, instead of testing the functions according to the expectations of the programmer, the requirements are being fulfilled as specified. The requirements should flow at the same time in the development team as well as the testing team, thus Singh advised testing firms to follow Waterfall or V nidel methodology.  

4.    Not implementing traceability across the life cycle
Although, testers don’t need to measure 100 per cent coverage, however whatever measure has been made should be done objectively and scientifically. But many of the testing firms do not measure the coverage and as per Singh’s views, this is another mistake that testing firms do. Thus, it is vital to use a Test Management System (TMS) and to apply two – way traceability.  

5.    Not analyzing the defects found in any of the testing to determine the cause
Only after identifying the root cause of the defect, a tester can fix the problem. Singh said that a Root Cause Analysis will help in reducing the number of defects in the upcoming software releases. The RCA analysis should be conducted not only at the end of the release but also after each test phase.

Don't Miss
Experts on QA
Swaid Qadir Bhat
Sr System Architect
Virtusa Corporation
Subhash  Motwani
Prasad Rao Pasam
Ayaskanta  Mohanty
Managing Director
TATWA Technologies
Rajesh  Dagar
Software Architect
Connect Icon Pvt Ltd
Yasar  Khuthub
Software QA Manager
Azure IT Solutions
Sunil  Bhat
Project Management
HCL Infosystems Limi
Sharad  Agarwal
Team Lead
Write your comment now
Reader's comments(1)
1: hi,
Here is a small correction in point number five. Tester never fix any issues. He will detect/find issues. Here correction required instead of Tester need Developer
"Only after identifying the root cause of the defect, a tester can fix the problem"
Posted by:Nandkumar Patil - 06 Sep, 2013
This report is the result of the largest public-private sector rese...
For those not familiar with the Coverity Scan™ service, i...