Be aware: Shipping quickly may Ship bugs
Shipping quickly may ship some bugs possibly as tester may not test the product exhaustively. But as quality assurance testing expert we should make sure that no major and critical bug should escape. All the critical and important flow must be covered. For example we shipped a CD and did not test that it should be auto run then this is major escape. As long as there are major bugs exist in a product it should not be shipped from a tester point of view. Minor and small UI bugs can be left aside. We may categorically mention that the product is being shipped with these known bugs.
Software quality assurance and Testing is a vital activity for creating a software and to assure quality. Software quality drives reputation and customer satisfaction. We are in an era were the software industry understands how essential it is to perform Software quality assurance&testing in order to create a high quality product. It has already been proven that performing testing at an early stage helps improve quality of a product and makes it reliable. Early shipping of a newly developed product without a cycle of testing can lead to blunders as the software would consist innumerous bugs which could not have been caught by the developers. An example of a quick shipment of software with bugs is "Ariane 5 rocket crash" which took place in June 1996. An incorrect line of code was the cause of the crash which resulted in a huge loss of half a billion dollars. The bottom line here is that it is necessary to conduct certain rounds of testing of product before its shipment in market as it would lead to a productive performance and satisfied customers.
Release date of any product should be decided after getting in and out of application and the number resources available for design, development and QA testing. If anything among these are left out, we won’t get a decent output. Shipping it early would definitely lead to a bad product. There have been many examples of early delivery failure wherein QA was not given proper time to find quality bugs which led to customer dissatisfaction and the product failed to make an impact. One can therefore agree with this point that shipping quickly may ship bugs.
Well, some of you may differ and believe that there are various quality improvement processes which helps the QA to deliver Quality products, if such processes are followed by QA then they can not only deliver Quality products but also in less time. On the other hand taking more time for QA does not promise the delivery of Quality Product. There are various factors such as complexity of the software, knowledge of tester, experience of tester, etc. that directly affects the Quality of product.
In most cases QA testing folks would agree that shipping quickly a product increases the chances of shipping bugs. If you are delivering a product quickly without thorough testing that definitely it contain bugs. Testing will never be done in a hurry. For testing any software you should have proper documentation, proper vision of the product, proper knowledge of its functionalities, priorities distribution is clear only than you can test the product and ship them.
Author:
Knowledge Sharing Team at QA InfoTech is responsible for research on new tools & technologies for effective quality assurance testingacross all industry verticals. QA InfoTech (an ISO 9001:2008 & CMMI III certified) is one of the leading Quality assurance Testing Companies with five testing “Centers of Excellence” in the United States and India. It offers end to end QA testing services.
Links:
https://plus.google.com/110881056047596544779/posts?hl=en
http://www.linkedin.com/groups/Software-Quality-Assurance-future-ahead-4435957?trk=my_groups-b-grp-v








