Project

General

Profile

Actions
Copy link

action #64610

closed

[functional[u] test fails in wireshark - test needs adaptations

Added by szarate about 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
SLindoMansilla
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 30
Start date:
2020-03-19
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

So preference window changed, now clicking on a preference, does not toggle it, but marks the field to be edited, old code was using assert and click, but it will have to use assert and click only after confirming that the selected option is protocol.

Another suggestion is to press spacebar instead, of assert and click

openQA test in scenario sle-15-SP2-Online-x86_64-we-module@64bit fails in
wireshark

Test suite description

Execute WE-related tests on SLE15 installations with WE module enabled (for products earlier than SLE15, the scenarios are we, we-ftp, we-http). Maintainer: okurz.

Reproducible

Fails since (at least) Build 160.1

Expected result

Last good: 156.8 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by SLindoMansilla about 4 years ago

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

Missing needles created
Waiting for verification on OSD

Actions
Copy link
 #2

Updated by SLindoMansilla about 4 years ago

  • Status changed from In Progress to Resolved

verfied on OSD

Actions
Copy link
 #3

Updated by okurz about 4 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: we-module
https://openqa.suse.de/tests/4111506

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #5

Updated by SLindoMansilla about 4 years ago

hjluo wrote:

we migration hit this on ooffice https://openqa.nue.suse.com/tests/4112380#step/ooffice/4 as your function test
https://openqa.nue.suse.com/tests/4111506#step/ooffice/4

This needle should work:

commit b20fcbaeeac8dd1daf9f62ab58d88cf9d0d6ca87
Author: Grace Wang <grace.wang@suse.com>
Date:   Mon Apr 13 03:47:54 2020 +0200

    ooffice-tip-of-the-day-20200413 for sle-15-SP2-Online-x86_64-Build176.1-wayland-desktopapps-documentation@64bit-virtio-vga

Verification run: https://openqa.nue.suse.com/tests/4117109 (running)

Actions
Copy link
 #6

Updated by SLindoMansilla about 4 years ago

Previous verification run failed because proxy SCC is not working.
Trying with hydra: https://openqa.suse.de/tests/4120631

Actions
Copy link
 #8

Updated by okurz almost 4 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: we-module
https://openqa.suse.de/tests/4171110

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link

Also available in: Atom PDF