Project

General

Profile

action #120834

[qe-core] tomcat: login to example app fails

Added by dimstar 3 months ago. Updated 9 days ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

From the looks of the test it seems like we're not even typing the username/password in the corresponding fields (but there is no video, so a bit hard to confirm)

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-tomcat@64bit fails in
tomcat

Test suite description

Maintainer: zluo@suse.de
Install and test tomcat on Tumbleweed.

Reproducible

Fails since (at least) Build 20221121

Expected result

Last good: 20221120 (or more recent)

Further details

Always latest result in this scenario: latest

History

#1 Updated by maritawerner 2 months ago

  • Subject changed from tomcat: login to example app fails to [qe-core] tomcat: login to example app fails

#2 Updated by dimstar 2 months ago

https://openqa.opensuse.org/tests/2910344#next_previous

In the last week, the test had about a 50% success rate

#3 Updated by openqa_review about 1 month ago

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

This bug is still referenced in a failing openQA test: tomcat
https://openqa.opensuse.org/tests/2974521#step/tomcat/1

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

#4 Updated by dimstar 25 days ago

Out of the last 10 runs, 50% failed, 50% succeeded

#5 Updated by zluo 24 days ago

  • Status changed from New to In Progress
  • Assignee set to zluo
  • Start date deleted (2022-11-22)

let me check this issue.

#7 Updated by zluo 24 days ago

the issue with check tomcat status can be resolved as above WIP PR.

but I cannot understand how login works in tomcat:

JspTest.pm

...
sub form() {
    assert_screen('tomcat-form-example', TIMEOUT);
    send_key('tab');
    send_key('down');
    for (1 .. 2) { send_key('ret'); }

    if (check_screen('tomcat-click-save-login', 60)) {
        assert_and_click('tomcat-click-save-login', timeout => TIMEOUT);
    }

    send_key('tab');
    type_string('tomcat');
    send_key('ret');
    wait_still_screen;
    assert_screen('tomcat-form-example-result', TIMEOUT);
}   
...

#8 Updated by zluo 23 days ago

  • Status changed from In Progress to Workable
  • Assignee deleted (zluo)

since this is more likely a performance issue and we considered already to re-write the tomcat module, I will stop to work on it for now.#

#9 Updated by openqa_review 9 days ago

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

This bug is still referenced in a failing openQA test: tomcat
https://openqa.opensuse.org/tests/3076658#step/tomcat/1

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Also available in: Atom PDF