Writers' Community!
Home News Business Science & Technology Life Style
Front Page Page Two Columnists Submit an Article FAQs Contact Author Login
Article Submission
We Need YOUR Articles!
We'll Promote Them for FREE!

Author Login

New Authors
Register Here


Now Serving 5,612 Authors
48,603 Quality Articles
& 6,459 Current Users Online!
Featured Authors
Joel Hendon (4,870)
Sandra E. Graham (2,260)
Robert Melaccio, Sr. (6,428)
Terry Mitchell (2,881)
Mike Fak (6,526)
Walter Rhett (2,655)
David Pekrul (802)
Barbara Clark (479)
Teresa Ortiz (4,920)
Jane Bullard (2,004)
Tex Norman (4,421)
Janice Tracy (148)
David Tanguay (7,680)
Mogama (12,506)

View All Featured Authors
Most Recent
DVD Software Explained and Clarified

Microsoft Word 2007 Ribbon Controls

Effective Use of MS Project Calendars

Excel for Beginners

The future of PowerPoint?

Shrink Your Technology - How to Work Anywhere, Anytime Out of a Backpack

TCP/IP protocols and configurations.

How TCP/IP and Routing Work

Outsourcing Work

Preventing Malware Downloads with a Spyware Adware Blocker

Home » Categories » Computers & Networking » Software » Defect Classification In Software Testing » Printer Friendly

Defect Classification In Software Testing

Rated 3.5 out of 5
No Reader Ratings Available ?
Rate It  /  View Comments  /  View All Articles submitted by D v Suresh
Submitted Sunday, May 25, 2008
D v Suresh (405)

Log in to become a member of D v Suresh's Fan Club!


This section defines a defect Severity Scale framework for determining defect criticality and the associated defect Priority Levels to be assigned to errors found software.

The defects can be classified as follows:

Critical: There is s functionality block. The application is not able to proceed any further.

Major: The application is not working as desired. There are variations in the functionality.

Minor: There is no failure reported due to the defect, but certainly needs to be rectified.

Cosmetic: Defects in the User Interface or Navigation.

Suggestion: Feature which can be added for betterment.

Defect Priority

The priority level describes the time for resolution of the defect. The priority level would be classified as follows:

Immediate: Resolve the defect with immediate effect.

At the Earliest: Resolve the defect at the earliest, on priority at the second level.

Normal: Resolve the defect.

Later: Could be resolved at the later stages.

Test Metrics in software testing:

Metrics are the most important responsibility of the Test Team. Metrics allow for deeper understanding of the performance of the application and its behavior. The fine tuning of the application can be enhanced only with metrics. In a typical QA process, there are many metrics which provide information.

The following can be regarded as the fundamental metric:

Functional or Test Coverage Metrics.

Software Release Metrics.

Software Maturity Metrics.

Reliability Metrics.

Mean Time To First Failure (MTTFF).

Mean Time Between Failures (MTBF).

Mean Time To Repair (MTTR).

Functional or Test Coverage Metric . It can be used to measure test coverage prior to software delivery. It provides a measure of the percentage of the software tested at any point during testing.

It is calculated as follows:

Function Test Coverage = FE/FT

Where,

FE is the number of test requirements that are covered by test cases that were executed against the software

FT is the total number of test requirements

Software Release Metrics

The software is ready for release when:

1. It has been tested with a test suite that provides 100% functional coverage, 80% branch coverage, and 100% procedure coverage.

2. There are no level 1 or 2 severity defects.

3. The defect finding rate is less than 40 new defects per 1000 hours of testing

4. Stress testing, configuration testing, installation testing, Nave user testing, usability testing, and sanity testing have been completed

Software Maturity Metric

Software Maturity Index is that which can be used to determine the readiness for release of a software system. This index is especially useful for assessing release readiness when changes, additions, or deletions are made to existing software systems. It also provides an historical index of the impact of changes. It is calculated as follows:

SMI = Mt - ( Fa + Fc + Fd)/Mt

Where

SMI is the Software Maturity Index value

Mt is the number of software functions/modules in the current release

Fc is the number of functions/modules that contain changes from the previous release Fa is the number of functions/modules that contain additions to the previous release

Fd is the number of functions/modules that are deleted from the previous release

Reliability Metrics

Reliability is calculated as follows:

Reliability = 1 - Number of errors (actual or predicted)/Total number of lines of executable code

This reliability value is calculated for the number of errors during a specified time interval.

Three other metrics can be calculated during extended testing or after the system is in production. They are:

MTTFF (Mean Time to First Failure)

MTTFF = The number of time intervals the system is operable until its first failure (functional failure only).

MTBF (Mean Time Between Failures)

MTBF = Sum of the time intervals the system is operable

MTTR (Mean Time To Repair)

MTTR = sum of the time intervals required to repair the system

The number of repairs during the time period .


D V Suresh is the author of blog MICROSOFT DOT NET and SOFTWARE TESTING






Reprint Rights

Log in to become a member of D v Suresh's Fan Club!

Comments on this article:


» left by alka from blr (143 days 9 hours ago.)
Reader Rating: 2.5 out of 5
A fantastic explanation....really helped me a lot.....pls keep on posting such articles..

Respond to this comment

» left by arvindyadav from mumbai (1 day 5 hours ago.)
Reader Rating: 2 out of 5
good description

Respond to this comment

Was this article helpful to you? Leave a Public Comment or Question:

 

This Article has been viewed 495 times.
Article added to SearchWarp.com on Sunday, May 25, 2008
View other articles written by D v Suresh (405)


If you found this article interesting, you may want to check out:

Disclaimer:  All information on this site is provided for informational purposes only! By no means is any information presented herein intended to substitute for the advice provided to you by any health care or other professional or organization.


Today's Most Popular
Introduction to DQL-Documentum Query Language

Linux Command Tutorials - Opening a Linux Terminal / Console to Run Linux Commands - Tutorial Help

FTPS (FTP over SSL) vs. SFTP (SSH File Transfer Protocol): What To Choose

Internet Explorer 7 (IE7) As a Ftp Client-Does Not Work

Elimination of Spooler Subsystem App problem. Easy and quick.

Improve PC Performance - 6 Tips You Must Know.

Linux Commands Tutorials - Using the ls Command with Examples of Options - A Hands-On Tutorial Help

Software Development Lifecycle (SDLC) - Overall Project Measurement

Defect Classification In Software Testing

What Shows Up On a Criminal Record Background Check?

Home  |  Page Two  |  FAQ's  |  Contact  |  Terms of Service  |  Article Submission Guidelines  |  Writers' Contests  |  Privacy  |  Mission / About
Copyright © 1999-2008 SearchWarp.com, All Rights Reserved - SearchWarp.com is an IcoLogic, Inc. Company