Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.

Qt Metrics 2 Backlog: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
mNo edit summary
(New items and modified priorities (**** to identify mandatory ones for launch))
Line 9: Line 9:
! Status !! Priority !! Item
! Status !! Priority !! Item
|-
|-
| in progress || *** || Get the actual testset parent (not the Qt5 where it was run)
| in progress || **** || Get the actual testset parent (not the Qt5 where it was run)
|-
|-
| idle || *** || Change build_number (int) to build_key (string) for the new-CI
| idle || **** || Change build_number (int) to build_key (string) for the new-CI
|-
|-
| idle || *** || Get testfunctions from xml
| idle || *** || Get testfunctions from xml
|-
|-
| idle || *** || Get testrows from xml
| idle || *** || Get testrows from xml
|-
| idle || *** || OS grouping (currently platform.os has quite many values, should we group e.g. all windows platforms into one on home page)
|-
| idle || *** || Change testset_run.testcases_xxx to total_xxx (terminology change)
|-
|-
| idle || ** || Database indexing (for performance)
| idle || ** || Database indexing (for performance)
|-
|-
| idle || ** || OS grouping (currently platform.os has quite many values, should we group e.g. all windows platforms into one on home page)
| idle || * || Database normalisation: result fields in the *_run tables should have a separate table instead of the enums (could also make the naming more flexible)
|-
| idle || * || Database normalisation: db_status table does not have a primary key (table holds just one row with the latest data)
|-
|-
| idle || ** || Change testset_run.testcases_xxx to total_xxx (terminology change)
| idle || * || Database normalisation: conf.features is not perfect design, instead a separate feature table should be used (how this information will be used in the end)
|}
|}


Line 30: Line 36:
! Status !! Priority !! Item
! Status !! Priority !! Item
|-
|-
| in progress || *** || Home page modifications (enable buttons)
| in progress || **** || Home page modifications (enable buttons)
|-
|-
| idle || ** || Summary graph
| idle || **** || Overview page
|-
|-
| idle || *** || Overview page
| idle || **** || Project page
|-
| idle || *** || Project page
|-
|-
| idle || *** || Project page: Link to log file
| idle || *** || Project page: Link to log file
Line 42: Line 46:
| idle || ** || Project page: Way to expand the range of builds, include dates to listed builds
| idle || ** || Project page: Way to expand the range of builds, include dates to listed builds
|-
|-
| idle || *** || Platform page
| idle || **** || Platform page
|-
|-
| idle || *** || Platform page: Link to log file
| idle || *** || Platform page: Link to log file
|-
|-
| idle || ** || Platform page: OS grouping
| idle || *** || Platform page: OS grouping
|-
|-
| idle || ** || Platform page: Configuration flag identification
| idle || ** || Platform page: Configuration flag identification
Line 56: Line 60:
| idle || * || Branch page
| idle || * || Branch page
|-
|-
| done || *** || Top failing testsets page
| done || **** || Top failing testsets page
|-
|-
| done || *** || Top flaky testsets page
| done || **** || Top flaky testsets page
|-
|-
| in progress || *** || Testset page
| in progress || **** || Testset page
|-
|-
| idle || *** || Testset page: Link to log file
| idle || *** || Testset page: Link to log file
Line 93: Line 97:
! Status !! Priority !! Item
! Status !! Priority !! Item
|-
|-
| idle || ** || Build phases by configuration (like in the old metrics page)
| idle || ** || Summary graph of current CI status
|-
| idle || ** || Build phases by configuration (like on the old metrics page)
|-
|-
| idle  || * || Build phases by configuration: Tick box to select if idle times are included or not in the Build phases graph
| idle  || * || Build phases by configuration: Tick box to select if idle times are included or not in the Build phases graph
Line 114: Line 120:
! Status !! Priority !! Item
! Status !! Priority !! Item
|-
|-
| idle || *** || Web security
| idle || **** || Web security
|-
| idle || *** || Utilise Ajax for better user experience
|-
| idle || ** || API to remove old data from the database (timescale fixed or selectable) keeping the referential integrity in mind
|-
|-
| idle || ** || Utilise Ajax for better user experience
| idle || ** || Branch archiving (default solution to delete from the db (API?), but could mark branches archived or something)
|-
|-
| idle || * || Progress bar when loading page or data
| idle || * || Progress bar when loading page or data
Line 147: Line 157:
! Status !! Priority !! Item
! Status !! Priority !! Item
|-
|-
| idle || ** || Implementation solution description
| idle || *** || Implementation solution description
|-
|-
| in progress || ** || Database design
| in progress || *** || Database design
|-
|-
| in progress || * || Class documentation
| in progress || ** || Class documentation
|}
|}

Revision as of 08:47, 5 June 2015

This is the backlog for Qt Metrics 2 site currently under development.

In case of proposals or improvement ideas please contact Juha Sippola (report builder, database) or Tony Sarajärvi (parser).

Data reliability and completeness (database and parser)

Status Priority Item
in progress **** Get the actual testset parent (not the Qt5 where it was run)
idle **** Change build_number (int) to build_key (string) for the new-CI
idle *** Get testfunctions from xml
idle *** Get testrows from xml
idle *** OS grouping (currently platform.os has quite many values, should we group e.g. all windows platforms into one on home page)
idle *** Change testset_run.testcases_xxx to total_xxx (terminology change)
idle ** Database indexing (for performance)
idle * Database normalisation: result fields in the *_run tables should have a separate table instead of the enums (could also make the naming more flexible)
idle * Database normalisation: db_status table does not have a primary key (table holds just one row with the latest data)
idle * Database normalisation: conf.features is not perfect design, instead a separate feature table should be used (how this information will be used in the end)

Pages and views

Status Priority Item
in progress **** Home page modifications (enable buttons)
idle **** Overview page
idle **** Project page
idle *** Project page: Link to log file
idle ** Project page: Way to expand the range of builds, include dates to listed builds
idle **** Platform page
idle *** Platform page: Link to log file
idle *** Platform page: OS grouping
idle ** Platform page: Configuration flag identification
idle * Platform page: Identification of configurations where insignificant or force success could be removed
idle * Platform page: Filtering mechanism
idle * Branch page
done **** Top failing testsets page
done **** Top flaky testsets page
in progress **** Testset page
idle *** Testset page: Link to log file
idle *** Testset page: Testset flag identification
idle ** Testset page: Testset run times
idle * Testset page: Filtering mechanism
idle * Testset page: Identification of testsets where insignificant could be removed
idle *** Testfunction page/information
idle *** Testfunction page/information: Testfunction flag identification
idle ** Testfunction page/information: Identification of testfunctions where blacklisting could be removed
idle ** Testfunction page/information: Link to xml file
idle * Testfunction page/information: Find skipped testfunctions
idle *** Testrow page/information
idle ** Top failed testfunctions page

Graphs

Status Priority Item
idle ** Summary graph of current CI status
idle ** Build phases by configuration (like on the old metrics page)
idle * Build phases by configuration: Tick box to select if idle times are included or not in the Build phases graph
idle * Build phases by configuration: Configuration result to the Build phases graph (e.g. to conf title)
idle * Build phases by configuration: Add tooltips into Build phases graph (e.g phase name and value)
idle * Visualize CI performance via testset execution time (to visualize sequential and parallel runs)
idle * Visualize CI performance via the trend of phase duration (one, or several if feasible) across the last 20 builds in selected Project Configuration
idle * Improvement progress trend graphs, e.g. on build success rates, build execution times, Configuration and Autotest force success and insignificant flag removals.

Other features

Status Priority Item
idle **** Web security
idle *** Utilise Ajax for better user experience
idle ** API to remove old data from the database (timescale fixed or selectable) keeping the referential integrity in mind
idle ** Branch archiving (default solution to delete from the db (API?), but could mark branches archived or something)
idle * Progress bar when loading page or data
idle * Link(s) to other related Qt Metrics
idle * Associate gerrit change ids with builds
idle * Include the bug id’s for test cases. This requires first a database or other solution where to get the data.
idle * Log file parsing helper (a way to find things in the last n logs)
idle * Register to receive error reports to a certain module (plus unregister)
idle * Report generator to create a detailed text & graph report from a view. This would be applicable for such data that takes long time to extract and format.
idle * Data export to excel/pdf from a view
idle * Identify which CI build machines failed most often and which CI builds take the longest time to execute
idle * Add Google Analytics to get information on the portal usage
idle * Support for https

Documentation

Status Priority Item
idle *** Implementation solution description
in progress *** Database design
in progress ** Class documentation
Retrieved from "https://wiki-qt-io-staging.herokuapp.com/index.php?title=Qt_Metrics_2_Backlog&oldid=17791"