Project

General

Profile

Actions

action #53351

closed

[opensuse] test fails in mate_terminal

Added by dimstar almost 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2019-06-20
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-NET-x86_64-otherDE_mate@64bit fails in
mate_terminal

Test suite description

Reproducible

Fails since (at least) Build 20190618

Expected result

Last good: 20190617 (or more recent)

Further details

Always latest result in this scenario: latest

Seems with the update to mate-terminal 1.22.1 there is now an extra question to close the window - something the openQA test does not anticipate

Actions #1

Updated by okurz almost 5 years ago

  • Status changed from New to In Progress
  • Assignee set to okurz

@dimstar I guess in cases like these, where it is pretty clear that the test module needs to be updated because the component it test has changed its behaviour in expected way, you can simply assign to the test module maintainer. So you can go into the source code of the test module, e.g. https://openqa.opensuse.org/tests/963346/modules/mate_terminal/steps/1/src and then you find … oh, it's you! ;)

So I guess in cases like these in particular please state who you would expect to take a look into the ticket, e.g. "[functional][u]" for the SUSE QA team QSF-u or "[opensuse]" for "casual openSUSE contributors + openSUSE RMs". So, I will take the ticket because I think I could do it easily but can you tell, what was your expectation?

Actions #3

Updated by dimstar almost 5 years ago

The expectation was pretty easy: I filed it to have a ticket number to attach to the test. From there on, I was planning to either convince the MATE distro maintainers to chime in - or, as the test lists me as maintainer (since I added MATE to the test setup, like the other OtherDE tests) - I'd have given it a shot at fixing it. So not really different from what your expectation was what should happen.

Actions #4

Updated by okurz almost 5 years ago

that's alright. My question was mainly if we can encode that "expectation" into a team-tag in the subject line. So in that case I guess "[opensuse]" would be the best matching tag. If we already put a team tag in the subject line at the time of ticket creation we save some work for people doing ticket triaging later following https://progress.opensuse.org/projects/openqatests/wiki#ticket-backlog-triaging

Actions #5

Updated by okurz almost 5 years ago

  • Subject changed from test fails in mate_terminal to [opensuse] test fails in mate_terminal
  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF