Details
-
Task
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
None
-
None
Description
The goal of the script is to create jira bugs in automatic way.
The script should be usable for for both blacklisted and flaky test cases. The jira connection part of the script is already done - and based on another project:
https://git.qt.io/kaabdelr/insignificant-bot
Insignificant bot however is using ML approach to connect test with jira compoment.
This approach would be simpler it would require mapping from source code to corresponding jira component
Map:
The map should be in the form key->value,
where key is list of keywords eg. ['gui', 'painting'] or ['gui', 'widet', 'layout'] (the lists are or different length but usually 2 or 3 elements)
the value is jira compoment (eg 'GUI:Painting')
eg
for test path:
./gui/painting/qpainter/tst_qpainter.cpp
keywords:
gui, painting, qpainter
in terms tuple:
(gui, painting, qpainter)
mapped Jira component
'GUI: Painting'
project repo containing: keywords, responses from maintainers is available at:
https://git.qt.io/qtqa/jira_test_report_bot
progress of work can be seen at:
https://intranet.qt.io/display/QTRD/Jira+bot+bug+reporting+tool
To do
change body of report:
- flaky/failes per function,
- early warning excluded
- estimasted number of blocked gerrit changes: qtbase x 5, other modules x 1
- check history - how many jira reports were already created for this test
change counting per test function - single report per test function
update qtbase
update qtDeclartive mapping from Mitch
+ check stats per platform (outliers)
Future notes:
- providing grouping mechanism for similar platforms (eg MacOS family) - so that it is not seen as "duplicate"
- change body of the report to add monthly information and add information of how many gerrit changes had to be restaged because of the ticket
- add mechanism to update changes in tests structures / new components
Done
2) making sure we do not make duplicates!
Attachments
1.
|
Jira component map | Open | Tero Heikkinen |