gherkin_script: Display failure details on pipeline run details #6062
Conversation
sanketpathak
force-pushed
the
gherkin_script_ODC-3713
branch
2 times, most recently
from
56d88d8
to
c0f82ca
Compare
...res/pipelines/pipeline-Display failure details on pipelineruns and taskruns-ODC-3713.feature
Outdated
Show resolved
Hide resolved
...res/pipelines/pipeline-Display failure details on pipelineruns and taskruns-ODC-3713.feature
Outdated
Show resolved
Hide resolved
sanketpathak
force-pushed
the
gherkin_script_ODC-3713
branch
from
c0f82ca
to
0ac858c
Compare
| @regression | ||
| Scenario: Display failure details of pipeline run in topology sidebar | ||
| Given user is in topology | ||
| And a node with failed pipeline is present |
There was a problem hiding this comment.
Not sure how much assumption here is... but did we want to say what "node with failed pipeline" is? Like
| And a node with failed pipeline is present | |
| And a node with an associated pipeline that has failed is present |
| Scenario: Display failure details of pipeline run in topology sidebar | ||
| Given user is in topology | ||
| And a node with failed pipeline is present | ||
| When user opens sidebar of the n ode |
There was a problem hiding this comment.
| When user opens sidebar of the n ode | |
| When user opens sidebar of the node |
| And user scrolls down to pipeline runs section | ||
| Then user will see the pipeline run name with failed status | ||
| And user will see failure message below pipeline runs | ||
| And user will also see the log snippet with horizontal scroller |
There was a problem hiding this comment.
Technically there is nothing saying it has to have a horizontal scroller. It is technically possible not to have it.
sanketpathak
force-pushed
the
gherkin_script_ODC-3713
branch
from
0ac858c
to
ead9f75
Compare
openshift-ci-robot
added
the
approved
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewballantyne, gajanan-more, sanketpathak The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest Please review the full test history for this PR and help us cut down flakes. |
https://issues.redhat.com/browse/ODC-4257