Geek Articles

Categories

 

Subscribe

Daily Updates Subscribe geekarticles update via email Subscribe geekarticles update via RSS

 
GeekArticles Testing Bug Reporting

Test Progress Reporting Using Functional Readiness

Author: stickyminds.com | Published: 18th Aug 2005 | Visited: 449 times | Add Comment
Filed in: Bug Reporting

One of the goals of testing is to find as many of the "big bugs" as possible while covering as much of the functionality as possible before the implementation date. On many projects the implementation date is not flexible and it is difficult to make a case to management for moving the date or at least considering the risk of implementing before making the decision. Management doesn't always get the "big picture" and detailed defect reports don’t always reflect risk. In order to help the project team and management assess risk and make decisions during the course of the project, there needs to be a way to express testing status in a comprehensive "big picture" view. Functional readiness is a way to simply describe test status in the context of risk. The Functional Readiness Matrix (FRM) is a decision-making tool that summarizes these metrics. An FRM is created for each phase of testing and the metrics contained in the FRM can be used as entrance criteria for the next phase of testing or for implementation.

Read Article
 

Sponsored Links

 


Related Articles

 Swing Extreme Testing - Outline of the Unit Test Outline of the Unit Test The things we want to test are: Initial settings: The text field is empty. The text field is a sensible size. The Ok button is disabled. The Cancel button is enabled. The dialog is a sensible size. ...

 Swing Extreme Testing - Unit Test Infrastructure Unit Test Infrastructure Having seen the broad outline of the test class and the UI methods needed, we can look closely at the implementation of the test. start with the UI Wrapper class and the init() and cleanup()method ...

 Swing Extreme Testing - The Constructor Test The Constructor Test A freshly constructed SaveAsDialog should be in a known state, and we need to check the things we listed at the start of this chapte ...

 Swing Extreme Testing - The wasCancelled() Test The wasCancelled() Test The first of our API tests is to check the wasCancelled() method. We will basically do three investigations. The first test will call wasCancelled()before the dialog has been cancelled. The second test will cancel the dialog and then call the method. In the third test we wil ...

 Swing Extreme Testing - The Data Validation Test The Data Validation Test The Ok button of the SaveAsDialog should only be enabled if the name that has been entered is valid. A name can be invalid if it contains an illegal character, or if it has already been use ...

 Enum Keyword And Its Functional Usage. This article describes 'Static Methods' of Enum Cl ...

 Designing Application Using Test Driven Development In this article we will take a look at designing application using test driven developm ...

 Advanced Ranking and Grouping with SQL Server Reporting Services Learn how to flexibly define a SQL Server Reporting Services report for ranking purposes. This article provides a workaround for custom grouping totals for top items and for jazzing the table up with some visual chart indicat ...

 Advanced Matrix Reporting Techniques Learn how to build robust Matrix-style reports in SQL Server Reporting Services. These advanced reporting techniques make it easier to build a fully-functional rep ...

 WinINet Test Application A WTL application to test asynchronous WinINet functional ...



Next: The Influential Test Manager



Post Comment

Name:


Email:
 (Optional. Used for Notification)

Title:

 
Comment:


Validation Code:
 <=>  (Enter this code in text box)





Latest Articles

 

Popular Articles

Sponsored Links