action #45887

openQA Tests - action #36709: [functional][y][epic] Improve informing about test scenarios

[functional][y] testsuite description on the test run page

Added by okurz 9 months ago. Updated 8 months ago.

Status:ResolvedStart date:09/01/2019
Priority:NormalDue date:12/02/2019
Assignee:andriinikitin% Done:

100%

Category:Feature requestsEstimated time:8.00 hours
Target version:SUSE QA tests - Milestone 22
Difficulty:
Duration: 25

Description

Acceptance criteria

  • AC1: The testsuite description can be found on each test run page

Suggestions

History

#1 Updated by okurz 9 months ago

  • Project changed from openQA Tests to openQA Project
  • Category changed from Enhancement to existing tests to Feature requests

#2 Updated by riafarov 8 months ago

  • Estimated time set to 8.00

#3 Updated by riafarov 8 months ago

  • Due date changed from 29/01/2019 to 12/02/2019

#4 Updated by andriinikitin 8 months ago

  • Assignee set to andriinikitin

assigning for investigation as discussed with okurz

#5 Updated by andriinikitin 8 months ago

  • % Done changed from 0 to 90

#6 Updated by andriinikitin 8 months ago

  • % Done changed from 90 to 100

#7 Updated by okurz 8 months ago

  • Status changed from Workable to In Progress

PR is merged, this is definitely "In Progress", right?

#8 Updated by andriinikitin 8 months ago

  • Status changed from In Progress to Resolved

#9 Updated by okurz 8 months 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.

#10 Updated by andriinikitin 8 months 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?

Also available in: Atom PDF