Home 
Testing Bug ReportingTest Progress Reporting Using Functional Readiness
Author: stickyminds.com Published: 10th Nov 2005 Visited: 928 times
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
• JMeter - Running the Test Running the Test Once the assertions are properly completed we are expecting that running our Test Plan would pass all the assertions Passed assertions will not show any error in Assertion Results Listener installed within the same scope As for all Listeners results as captured by the Listeners can ...
• JMeter - Functional Testing Functional Testing JMeter is found to be very useful and convenient in support of functional testing Although JMeter is known more as a performance testing tool functional testing elements can be integrated within the Test Plan which was originally designed to support load testing Many other load te ...
• SOA Web Services - Developing the Test Client Developing the Test Client We will now develop a C console application for consuming the previously created web services Use the project wizard in VS NET to create a console applica ...
• 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 ...
• 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 met ...
• 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 will enter a ...
• 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 ...
• Infinite Progress Panel Demo In his blog on JavaFX Script James Weaver discusses some uses of Romain InfiniteProgressPanel widget in the JavaFX Script UI library Weaver promises demos of more UI widgets in future p ...
