From: "halamour at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: bunsen@sourceware.org
Subject: [Bug bunsen/31364] New: Introduce test case navigation feature
Date: Fri, 09 Feb 2024 20:14:35 +0000 [thread overview]
Message-ID: <bug-31364-12167@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31364
Bug ID: 31364
Summary: Introduce test case navigation feature
Product: bunsen
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: bunsen
Assignee: bunsen at sourceware dot org
Reporter: halamour at redhat dot com
Target Milestone: ---
Currently, tracking a single test case across multiple test runs is difficult
in bunsen. There is no way to know where/when a single test was run and under
which test-runs.
This feature will allow users to select a single test/subtest from a testrun in
bunsen to track, then (from separate test-runs) filter and select the results
of the same subtest and display all this information in a grid.
The grid will be similar to r-httpd-browse but with an emphasis on tracking the
results of a single test and with more customization regarding what information
is displayed and how it is displayed. This will include configuring the grid's
horizontal and vertical axis.
This will work with a python reporting script that will take the selected
test's testrun# commit and expfile/subtest name as input context and use it to
fetch the test results that match the filters from bunsen.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2024-02-09 20:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-31364-12167@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=bunsen@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).