Qt Metrics 2 Backlog: Difference between revisions

Revision as of 11:53, 18 June 2015

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

The priority **** items are the core functionality and would be the target prior to launch or wider use.

The priority *** items are considered content/functionality for basic use as requested by the key stateholders.

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

Status	Priority	Item
in progress	****	Get the actual testset parent (not the Qt5 where it was run) (Code Review)
in progress	****	Change build_number (int) to build_key (string) for the new-CI
idle	***	Get testfunctions from xml
idle	***	Get testrows from xml
in progress	***	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)

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: 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 (Code Review / UI, Code Review / parser)
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

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.

Status	Priority	Item
in progress	****	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

Status	Priority	Item
idle	***	Implementation solution description
in progress	***	Database design
in progress	**	Class documentation

@@ Line 13: / Line 13: @@
 ! 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) ([https://codereview.qt-project.org/#/c/114432/ Code Review])
 |-
 | in progress || **** || Change build_number (int) to build_key (string) for the new-CI
@@ Line 60: / Line 60: @@
 | idle || * || Branch page
 |-
-| done || **** || Top failing testsets page
+| done || **** || Top failing testsets page ([https://codereview.qt-project.org/#/c/113921/ Code Review / UI], [https://codereview.qt-project.org/#/c/114211/ Code Review / parser])
 |-
 | done || **** || Top flaky testsets page
@@ Line 120: / Line 120: @@
 ! Status !! Priority !! Item
 |-
-| idle || **** || Web security
+| in progress || **** || Web security
 |-
 | idle || *** || Utilise Ajax for better user experience