agile FACT Report
An agile FACT Report provides visibility to Product Owners, Stakeholders, and any other interested party to the true progress of each Story that make up a Feature within a Sprint.
Pending - The Story is incomplete as there are Scenario that are currently being worked on.
Complete - All Scenarios associated with a story have passed.
Failed - One ore more Scenarios associated with a story have failed.
The FACT Report is linked directly to the application code executing in a test environment (Local, UAT, Staging etc.) giving a real-time progress of each Story being developed.
The FACT Report provides mulitmedia artifacts in the form of video, slides or screenshots that are reviewed by the Product Owner in order to Confirm that a Story has been built as specified. Multimedia artifacts provide a greater level of information and thus confidence to a wider audience than the traditional green/red lights or pass/fail symbols in standard Test Reports.
Pending - The Story is incomplete as there are Scenario that are currently being worked on.
Complete - All Scenarios associated with a story have passed.
Failed - One ore more Scenarios associated with a story have failed.
The FACT Report is linked directly to the application code executing in a test environment (Local, UAT, Staging etc.) giving a real-time progress of each Story being developed.
The FACT Report provides mulitmedia artifacts in the form of video, slides or screenshots that are reviewed by the Product Owner in order to Confirm that a Story has been built as specified. Multimedia artifacts provide a greater level of information and thus confidence to a wider audience than the traditional green/red lights or pass/fail symbols in standard Test Reports.
Regression Testing
At any time during the Development Cycle a suite of automated acceptance tests within the agile FACT Report can be triggered to execute a range of Stories/Features to ensure no defects have been introduced into the system.