Skip to content

chapter-webgui.pod

Latest commit

 

History

History
192 lines (120 loc) · 4.68 KB

chapter-webgui.pod

File metadata and controls

192 lines (120 loc) · 4.68 KB

Web User Interface

The Web User Interface is a frontend to the Reports database. It allows to overview reports that came in from several machines, in several test suites.

It can filter the results by dates, machines or test suite, gives colorful (RED/YELLOW/GREEN) overview about success/failure ratios, allows to zoom into details of single reports.

To evaluate reported test results in a more programmatic way, have a look into the DPath Query Language that is part of the "Reports API".

Usage

The main URL is typically somerthing like

http://tapper/tapper

Understanding Tapper Details

Part 1 Overview

  • Go to http://tapper/tapper/reports

  • Click ``Last weeks test reports'', aka. http://tapper/tapper/reports/date/7

  • Below day ``Wed Oct 7, 2009'' find the line

    20856  2009-10-07  Topic-xen-unstable  satyr  PASS testrun 9617

  • Note that there are other reports in this group that are greyed-out, i.e. all report ids of this testrun are:

    20856    Topic-xen-unstable
20855    LMBench
20854    CTCS
20852    Host-Overview
20851    Hardwaredb Overview

  • Note that something FAILed in the CTCS run (20854).

  • What we know until here:

    • It is a test for Xen-unstable (Topic-xen-unstable)

    • The running of the guests+suites itself worked well (20856 PASS)

    • There were 2 guest runs:

      LMBench      satyr:celegorm                  PASS
CTCS         satyr:eriador                   FAIL

  • Click on the ID link ``20856'' aka. http://tapper/tapper/reports/id/20856

Part 2 Details

  • Here you see the details of this report 20856.

    You see:

    • green PASSED results for the ``MCP overview''. This means the starting and finishing of the guests worked.

    • attachments of console logs.

    • some links to more information (raw TAP report, preconditions)

  • Note below the group of all the other reports, again it's the group of those IDs:

    20856    Topic-xen-unstable
20855    LMBench
20854    CTCS
20852    Host-Overview
20851    Hardwaredb Overview

  • The most meta information is in ``20852 Host-Overview''.

  • Click on the ID link ``20852'' aka. http://tapper/tapper/reports/id/20852

  • Now you see the details of ``20852 Host-Overview'' with lots of meta information as ``Context''.

    You see:

    Metainfo
    cpuinfo: 1x Family: 15, Model: 67, Stepping: 2
    ram:     3950 MB
    uptime:  0 hrs

XEN-Metainfo
    xen_dom0_kernel:         2.6.18.8-xen x86_64
    xen_base_os_description: SUSE Linux Enterprise Server 10 SP2 (x86_64)
    xen_changeset:           20273:10cfcbef68ee
    xen_version:             3.5-unstable

guest_1_redhat_rhel5u4_32bpae_qcow
    xen_guest_description:  001-lmbench
    xen_guest_flags:        ...
    xen_guest_start:        ...

guest_2_suse_sles10_sp3_gmc_32b_up_qcow
    xen_guest_description:  002-ctcs
    xen_guest_flags:        ...
    xen_guest_start:        ...

  • If you are interested in what went wrong in the CTCS run, click on ID link ``20854'' aka. http://tapper/tapper/reports/id/20854

  • Here you see

    • one RED bar in CTCS-results

    • several RED bars in var_log_messages

    You can click on them to unfold the details.

Part 3 Testrun

  • Imagine that the testrun completely failed and no usable reports arrived in, except that primary one from the MCP, then you can use the link at the end of the line

    20856  2009-10-07  Topic-xen-unstable  satyr  PASS testrun 9617
                                                   ------------

  • Click on that link ``testrun 9617'' aka. http://tapper/tapper/testruns/id/9617

  • That contains the description what was planned in this testrun, regardless of whether it succeeded.

    (That's the main difference between the two complementary concepts ``Testrun'' vs. ``Reports''. The ``Testrun'' contains the specification, the ``Reports'' contain the results.)

    You see:

    Name                  Automatically generated Xen test
Host
    Architecture      linux64
    Root image        suse_sles10_sp2_64b_smp_raw.tar.gz
    Test              metainfo
Guest number 1
    Architecture      linux32
    Root image        redhat_rhel5u4_32bpae_qcow.img
    Test              py_lmbench
Guest number 2
    Architecture          linux32
    Root image    suse_sles10_sp3_gmc_32b_up_qcow.img
    Test              py_ctcs

  • That's it, basically.