Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

User will be to view and download the various reports of Build Execution Results, Device Usage, Script Health & Script Execution Time reports from the Reports section.

...

5.1 Execution Results

From execution results page, user can view the results of the triggered build executions. It shows the total count of test steps and its Pass, Fail, NT(Not Tested), NR(Not Run) and NA(Not Applicable) counts.

...

You can verify the required information from the Execution Result Details for that particular build.

...


5.2 Execution Results – TC

User can get an idea on the execution results from test case count via this page.

...

Following details will be displayed as shown below:

...


5.3Device Usage Report

User will be able to generate the usage reports of a particular device within the required dates.

...

The following data/details of that particular device will be generated as shown below.

...


5.4Script Health Report

User can generate the Health Report of the test scripts.

...

Also, by clicking on Download Report you can download the report to your local in order to see the data offline.

...

5.5Script Execution Time Report

User can generate the Execution Time Report of the test scripts for the required dates.

...

Also, by clicking on Download Report you can download the report to your local in order to see the data offline.

...


     RDK E2E Manager

RDK/CI portal sends execution requests to Automatics orchestration. Automatics based on filters configured decides if execution to be performed or not.

...

  • E2E RDK Request
  • E2E RDK Request Filter

...

6.1 E2E RDK Request

User will be able to see the incoming RDK Requests from the RDK Portal from this page.

...

If the request status is accepted, then execution will be triggered by Jenkins. Or else if the status is REJECTED, then no execution will be triggered.

  

...

6.2 E2E RDK Request Filter

User can configure RDK filters so that when request comes from RDK portal, Automatics can decide based on it, if execution should trigger or not.

...