Actions
action #45887
closedopenQA Tests - coordination #36709: [functional][y][epic] Improve informing about test scenarios
[functional][y] testsuite description on the test run page
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
SUSE QA - Milestone 22
Start date:
2019-01-09
Due date:
2019-02-12
% Done:
100%
Estimated time:
8.00 h
Description
Acceptance criteria¶
- AC1: The testsuite description can be found on each test run page
Suggestions¶
- Research which source code controls the display of content on each "test run page", e.g. the files within https://github.com/os-autoinst/openQA/tree/master/templates/test, maybe just https://github.com/os-autoinst/openQA/blob/master/templates/test/infopanel.html.ep which is the colored box on the top of each test run page
- Provide a unit test addition for openQA, e.g. in https://github.com/os-autoinst/openQA/blob/master/t/ui/18-tests-details.t#L105
- Make sure you can call the test and it fails
- Try to access the testsuite data from the template page source code
- If necessary provide controller functions that can be accessed from the page template code
- Include the testsuite description in the test run page
Updated by okurz over 5 years ago
- Project changed from openQA Tests to openQA Project
- Category changed from Enhancement to existing tests to Feature requests
Updated by riafarov over 5 years ago
- Due date changed from 2019-01-29 to 2019-02-12
Updated by andriinikitin over 5 years ago
- Assignee set to andriinikitin
assigning for investigation as discussed with okurz
Updated by andriinikitin about 5 years ago
- % Done changed from 0 to 90
Updated by okurz about 5 years ago
- Status changed from Workable to In Progress
PR is merged, this is definitely "In Progress", right?
Updated by andriinikitin about 5 years ago
- Status changed from In Progress to Resolved
Updated by okurz about 5 years ago
I could confirm the feature to be working ok in a quick test on my own instance of openQA. However I wonder about the line breaks within the description which seem to be ignored.
Updated by andriinikitin about 5 years ago
okurz wrote:
I could confirm the feature to be working ok in a quick test on my own instance of openQA. However I wonder about the line breaks within the description which seem to be ignored.
It is HTML behavior of <div> tag. If we need multiline - the quickest ways I see at the moment:
- replace carriage returns with <br> (kind of ugly from programming point of view)
- use <pre> tag instead of <div> (may look ugly in UI)
- format similar to https://github.com/os-autoinst/openQA/blob/5f691a07e5a29104289d59bce8a385a30ec738e5/templates/test/settings.html.ep#L8 (probably the way to go?)
Maybe some expert can recommend the best way to do it?
Actions