Filtering test results in Ibutsu’s frontend is designed expose SQLAlchemy’s filtering operations to the user. For all filters, the following translation is used:
|Operator||String Name||SQLAlchemy Example||Description|
||Does not equal|
||Greater than or equal to|
||Less than or eqaul to|
||Regex match that
||Column exists and is defined|
The information for this table is taken from filters.py.
Filtering the results/runs tables¶
Filtering the results and runs tables is done via select dropdowns that correspond to:
- column (also called
fieldin the UI)
- operator (shown with the ‘string name’ in UI)
Where column is a column on the
Result table, operator is one of the string names in
the table above, and value is the desired value by which you’d like to filter.
The select dropdowns give several options for
column, but it is possible to enter your own column
if it is not shown. Just type any desired column.
Note: The available columns are shown in the DB models for Runs/Results.
In the BE and FE,
metadata is translated to the
data column in the DB.
It is also possible to auto-apply a filter by clicking the blue pill labels that appear in the Run/Results
table. These will automatically filter results/runs by
Comma-separated list of filters¶
There are two places in the UI where a user is able to enter a comma-separated list of filters:
additional_filtersparameter when creating a new widget
Filterfield when building a report
These are simple text input components that take a string of comma-separated filters. Here, a user
is meant to use the
operator in the table above to filter on the appropriate column. Some examples
of these filters include: