Checkpoint & Test Reporting in QTP

Checkpoint & Test Reporting in QTP

Test Reporting Enhancements :

86. Ability to create reports in different format. Excel, Word, HTML etc…

87. Reporting of errors or failure in different categories and priority. E.g. – Reporting a error with severity, priority and category (Application, Script, Validation, Checkpoint).

88. Exact location of the error in the script. This should include the line of code, error number, error statement.

89. Direct ability to send report to a specified list of email addresses when the test end.

90. Currently the reports can only be viewed through QTP reporter viewer and cannot be viewed on machines without this tool. Report should be made completely Web compatible so that I can be viewed in any browser in the same way it is displayed in report viewer.

91. Ability to view status of current Action. Currently Reporter.RunStatus only provides the status of whole test and not for current action.

92. Ability to enumerate the current status from within a Test i.e. Actions executed with details, checkpoints executed with details, recovery scenarios executed with details.

93. Hosting web server to capture and display script status in batch.

94. Ability to report to a existing result file.

95. Ability to override the Action Name in reports.

96. Ability to specify the time zone to be used in reports.

97. Ability to specify the results path during the run

Checkpoint Enhancements :

98. Ability to alter properties of all checkpoints during run-time. E.g. Expected bitmap of a bitmap checkpoint, expected values of a Table/DB checkpoint etc.

99. Ability to create checkpoints at run-time.

100. Ability to load checkpoints from a external file at run-time.

101. Ability to enumerate all checkpoints present in current script.

Post a Comment

Previous Post Next Post