roperty="og:url" content="https://rokittech.com/index.php/about-us/blog/item/16-how-to-measure-quality" />
Anju Jain is the Head of Delivery for Testing Practice at ROKITT. Prior to joining ROKITT, she led large Transformation Programs and QA teams at various organizations like Deutsche Bank and Morgan Stanley. She has been instrumental in improving overall quality of the products and in bringing positive change in the organizations.
Background: Enormous amounts of data are processed every day. 8 million mobile payments were made in Q1 2015 at Starbucks, 3 Million – 5 Million trades are completed at NYSE on a daily basis, and 26.2 Billion credit card transactions were done in United States 2012.
Weekly # of mobile app transactions processed by Starbucks stores in the US as of Q1 2015 (in millions)
A lot has been written on how to measure various aspects of software development. The metrics range from lines of code, security defects to user satisfaction. In any scientific measurement effort, you must balance the sensitivity and the selectivity of the measures employed.
No metric is perfect. We need to understand which of the metrics make the most sense and contribute to a well-balanced and informed decision making. Software quality is a multi-dimensional concept. The views of a developer vary vastly from those of a business sponsor to an end user. One way of defining software quality is - Quality is a measure of how well the product serves its customers.
Mobile applications have now become a part of life. It’s common for users of smart phones, tablets and other mobile devices to download applications from the online store. The focus has considerably moved from the web to the mobile.
As it stands, most mobile devices use one of the two dominant operating systems: Google-developed Android and the Apple-developed iOS. The difference between these operating systems and their related devices isn’t just aesthetic: Just as your MacBook won’t run a Windows application, an Android phone can’t run an app built for iPhone — in most cases at least.
The purpose of testing is to ascertain that the product is built to its specifications and a quality product is released to the consumers.
Testing is an important step but we seem to be caught up in the cost, ROI, and measuring quality of the testing organizations to the extent that the basic premise of why we test is lost.
The goal of testing is to ensure the product is built to its specifications, not to run all tests and find tons of defects. Techniques, technologies and process can be employed to test faster, better and more accurately.