Now that we've added properties, we need a slightly larger window to
display everything clearly.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
Along with Property, PropertyValue, and PropertyFilter objects that are used
togther to show specific properties to the user when placed in a
Gtk.ColumnView.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
And convert our other Factory instances to inherit from it. This lets me
set up a Gtk.Inscription() in a singe way that is used everywere, and
abstract out some other binding code to make implementing new factories
easier.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
The XunitList implements the Gio.ListModel interface, and builds in some
virtual functions to query and fill out the rows in the list in a
standard way. I also update the TestCaseList and SummaryList to both
inherit from this class.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This Object is intended to be returned by a Gio.ListModel to show
Xfstests xunit information. I change the TestCase and Summary classes to
inherit from this class, removing a lot of duplicated code.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
I use the XunitCell as a base class for the (renamed) TestResult and
SettingsValue objects. This lets us combine common values and
functionality in one reusable place.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
The SummaryView displays a summary of the passed, failed, and skipped
tests for each xunit along with the time it took the xunit to run.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This is a Gtk.ListItemFactory that creates a Label widget and binds
xunit summaries to it. I use the summary field name to apply an
appropriate CSS class to each label.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
I add a global SizeGroup to the LabelFactory so the first column of each
table I make can have the same width. I also add style classes that are
applied with specific item values, which will mostly be used by the
SummaryView labels.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This is a list model designed to show a summary of xfstests results for
a given runid. I create a new one whenever the Application changes the
runid.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
And control the filter using the newly-created FilterButtons class. This
lets us hide completely skipped tests by default, since those are mostly
noise. I also add some custom icons used by the buttons to indicate
passed, failed, or skipped tests.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This is a Gtk.Button that has been customized to act similarily to a
Gtk.ToggleButton, but instead of giving the button a "pressed in" look
it changes the opacity of the displayed icon.
I'm planning to use this in the window headerbar in a set of buttons
designed to controll testcase filter state.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
I use the ResultFactory to do this. I also create a custom css
stylesheet to use for each cell in the Gtk.ColumnView displaying the
results. This lets us add custom colors so we can easily see at a glance
what is failing, passing, or skipped.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This is a Gtk.ListItemFactory that creates a Label widget and binds
testcase results to it. I use the result status as the name of a CSS
class that will be created in the next patch so the ColumnView cells
have a nicer presentation.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
The XfstestsView contains the TestCaseView, and will eventually contain
other views used to display test results and information.
For the moment, the TestCaseView displays the name of the testcases in a
single Xfstests run in a single column. I plan on adding more columns in
the near future.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This is a list model designed to show xfstests results for a given
runid. I create a new one whenever the Application changes the runid.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This is an empty Adw.Window with a headerbar configured to display the
application name. I also bind the Application runid property to the
Window to print out the currently displayed run.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This argument is passed to the Application using the 'command-line'
signal, so a running Application can switch to a new runid when
requested.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This command doesn't do much at the moment, it simply sets up the Gtk
Application and then exits. The actual UI will be built up over the next
several patches.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This command is used to garbage collect the xfstestsdb sqlite database.
It removes xfstests runs that have no added xunits, and runs older than
180 days that have not been tagged.
Implements: #16 (`xfstestsdb gc`)
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This command is used to garbage collect the xunit table by removing
xunits that have no testcases. This could be expanded on later to add
more removal conditions, such as xunits older than some age.
Implements: #15 (`xfstestsdb xunit gc`)
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
I found that deleting an xunit from the database was very, very slow.
This patch addresses the issue by adding additional indexes on the
link_xunit_properties table to make it easier to find properties that
are still in use. I also rework the `cleanup_xunit_properties` trigger
to only check propids that were used by the deleted xunit.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
I found that deleting an xunit from the database was very, very slow.
This patch addresses the issue by adding additional indexes on the
testcases table to make it easier to find messages that are still in
use. I also rework the `cleanup_testcase_messages` trigger to only check
messageids that were used by the deleted testcase.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
Right now it doesn't do any extra changes to the database besides
bumping the user_version to '2'. I'll fill it out over the next several
commits.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This function builds on the built-in Python function, and adds in
opening and reading the file in a way that can be used for running
generic scripts on the database.
I also take this chance to move SQL scripts into a subdirectory to keep
them together.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
The xfstests xunit generation has been updated to include an xml
namespace and add some extra attributes to the root element. This broke
my xunit parsing code, which is fixed with this patch.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
I install to /usr/local by default, but this can be overridden by
setting PREFIX when running `make`
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This command generates a table from the testcases that have been added
to a single run so the results of each testcase can be seen
side-by-side.
Implements: #9 (`xfstestsdb show`)
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This command shows detailed information about a specific testcase. The
'--maxlines=' option can be used to control the number of lines printed
from the system logs.
Implements: #13 (`xfstestsdb testcase show`)
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This command prints out information about the known testcases. It has
extra options to filter by runid, device, xunit, testcase, and status.
Implements: #11 (`xfstestsdb testcase list`)
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This subcomand doesn't actually do anything. It'll act as a hub for
testcase related subcommands instead.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
I use the testcases table to store testcase information, and store
messages, system out, and system error logs in the messages table.
The testcases_view is used to link testcases with their source xunits,
messages, system out, and system error logs. This view has an INSTEAD
OF INSERT trigger to allow insertions that properly set up message ids
in the testcases table.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This command prints out (key, value) pairs for each xunit property in
the database. It has options to filter by runid, xunit name, property
name, and value.
Implements: #14 (`xfstestsdb xunit properties`)
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
I use the xunit_properties table to store unique (key, value) pairs. The
link_xunit_properties table is then used to link properties to xunit
files.
I also make sure that properties are cleaned up when xunits are deleted,
but that we hang on to properties still in use by other xunits.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This command prints out information about the known xunit files. It has
extra options for filtering by runid, device, name, and hostname. I also
gave it optional Timestamp and Results columns that the user can enable.
Implements: #12 (`xfstestsdb xunit list`)
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
This is an optional column that can be enabled by passing "--xunit" as
an option. The "--xunit" option takes an optional string that can be
used to filter results by a specific xunit pattern.
Signed-off-by: Anna Schumaker <anna@nowheycreamery.com>
Anna Schumaker