UPT - Build wise trending report

This is a dashboard of preconfigured trending reports across various builds and executions of UPT. It helps analyze the increase in or change to test coverage in every build for any given artifact. The trending reports provide analysis on certain metrics captured by UPT and the reports can be enhanced to include other trending data as well. Each report can be drilled down further. You can also filter to compare two or more builds or filter on Build Number or Event Method.

UPT Dashboard

This is the main dashboard displaying analytic reports in a single view. You can filter the dashboard on one or more build numbers and drill down each report. Some of the salient reports are:

• Application User View. Displays count of a given user against any application such as number of times user SADMIN was used to log in to Siebel Communications Application for the test cases for a given build.
• Application Access. Displays count of web login versus number of times a view was activated for various applications.
• Login Across Apps. Displays count of various logins used for running the test cases across various applications.
• Applet Record Action. Displays count of various artifacts such as applications, applet, or views used to run a set of test cases for a given QA execution of test cases.

UPT Graphical Reports

This dashboard contains graphical reports that can be filtered on build number. Some salient reports are:

• Applet Access. Displays the number of times a given applet was accessed across test cases.
• Applet Displayed. Displays the number of times a given applet was displayed and limits the report to applets that were displayed more than 500 times.
• Applet with Invoke Method. Displays count of the number of times the invoke method for applets was used along with names of applets.

UPT - IRM Intersection

This dashboard is the intersection of IRM with UPT. It provides details on:

• Repository artifacts that are new or modified and also used by a customer. This report can be filtered on the applications used by the customer.
• Schema changes and workflow processes that are new or modified for a given upgrade path. These two artifacts are for the complete set of applications that Siebel supports and are not limited to any one application.