Actions
action #13850
openShow the exact source (file and line number) of a test API function call in test details
Start date:
2016-09-21
Due date:
% Done:
0%
Estimated time:
Description
Problem¶
Consider the following test details: https://openqa.opensuse.org/tests/266765#step/amarok/14
It is not obvious why a GNOME bug reference occurs in the KDE test. Displaying the exact line in the source where the error occurred would make the reason more clear.
Acceptance criteria¶
- AC1: The file path and line number of a test API call within the test distribution is shown in the test details
Suggestions¶
- Save which line of code triggered for instance recording the soft fail, e.g. like https://github.com/os-autoinst/os-autoinst/blob/1b6d94a7605791c41297b93771dac0082eb1856f/bmwqemu.pm#L221 does
- Display the information in the web UI
Updated by coolo about 7 years ago
- Target version set to future
the thing with line numbers is tricky - as it conflicts with higher goals of making the tests less perl intensive.
Updated by okurz about 5 years ago
- Subject changed from Show the exact source of an event in testdetails to Show the exact source (file and line number) of a test API function call in test details
- Description updated (diff)
- Status changed from New to Workable
Actions