Session Based Report For Narrator - 2nd Oct 2009
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Session Based Report For Narrator - 2nd Oct 2009 as PDF for free.
More details
- Words: 376
- Pages: 4
CHARTER To Test the Testability of Narrator Application
#AREAS OS | Windows XP SP3 Build | Not Available Product | Narrator Strategy | Complex | Testability Testing
START 2nd Oct 2009 12.40 PM
TESTER Parimala Shankaraiah
TASK BREAKDOWN None
#DURATION Normal - 45 minutes
#TEST DESIGN AND EXECUTION 70
#BUG INVESTIGATION AND REPORTING 30
#SESSION SETUP 0
#CHARTER VS. OPPORTUNITY 100/0
DATA FILES None
TEST NOTES 1. Testability is the test support included in the Software Product Code. Slightly hard to figure out what to test. 2. Though narrator appears to be simple in functionality, it poses a challenge in terms of providing a small dialog with little information about Events, typed characters etc 3. Test Interface is pretty simple and user friendly
OPPORTUNITY Observed a lot of functional issues – future charter
BUGS #BUG 1 Testability: No Access to Source code of narrator, design documents and the change records(If I was in the testing team of Narrator application) Repro: 1. Look for Source Code, design documents and the change records if any.
Result: Nothing is available for the tester Expected: As part of testability, there should be access to source code, design documents and the change records if any. This will help testers to read the code and interpret the code.
#BUG 2 Testability: Logging is not supported by Narrator Repro: 1. Look for any logs generated while Narrator is in use Result: No logs are available Expected Results: Having log information is very critical for testing the product because it is a good place to store error information as logs help uncover a lot of failure scenarios
#BUG 3 Testability: Event Viewer does not capture any log information about Narrator application Repro: 1. Start > Run > Eventvwr > Look for events related to Narrator Result: Event Viewer does not capture any log information about Narrator application Expected Result: Event logs are useful as a monitoring mechanism to observe failures which do not show up directly and hence should be supported.
#BUG 4 Testability: Uninstallation option is not provided Repro: 1. There is no option to uninstall Narrator Result: There is no option to uninstall Narrator
Expected Result: Uninstallation provides vital information and hence this option should be provided to the tester
ISSUES None
#AREAS OS | Windows XP SP3 Build | Not Available Product | Narrator Strategy | Complex | Testability Testing
START 2nd Oct 2009 12.40 PM
TESTER Parimala Shankaraiah
TASK BREAKDOWN None
#DURATION Normal - 45 minutes
#TEST DESIGN AND EXECUTION 70
#BUG INVESTIGATION AND REPORTING 30
#SESSION SETUP 0
#CHARTER VS. OPPORTUNITY 100/0
DATA FILES None
TEST NOTES 1. Testability is the test support included in the Software Product Code. Slightly hard to figure out what to test. 2. Though narrator appears to be simple in functionality, it poses a challenge in terms of providing a small dialog with little information about Events, typed characters etc 3. Test Interface is pretty simple and user friendly
OPPORTUNITY Observed a lot of functional issues – future charter
BUGS #BUG 1 Testability: No Access to Source code of narrator, design documents and the change records(If I was in the testing team of Narrator application) Repro: 1. Look for Source Code, design documents and the change records if any.
Result: Nothing is available for the tester Expected: As part of testability, there should be access to source code, design documents and the change records if any. This will help testers to read the code and interpret the code.
#BUG 2 Testability: Logging is not supported by Narrator Repro: 1. Look for any logs generated while Narrator is in use Result: No logs are available Expected Results: Having log information is very critical for testing the product because it is a good place to store error information as logs help uncover a lot of failure scenarios
#BUG 3 Testability: Event Viewer does not capture any log information about Narrator application Repro: 1. Start > Run > Eventvwr > Look for events related to Narrator Result: Event Viewer does not capture any log information about Narrator application Expected Result: Event logs are useful as a monitoring mechanism to observe failures which do not show up directly and hence should be supported.
#BUG 4 Testability: Uninstallation option is not provided Repro: 1. There is no option to uninstall Narrator Result: There is no option to uninstall Narrator
Expected Result: Uninstallation provides vital information and hence this option should be provided to the tester
ISSUES None
Related Documents
Session Based Report For Narrator - 2nd Oct 2009
June 2020 4
Narrator
June 2020 17
Pe Report Oct 2009
June 2020 9