Project

General

Profile

Actions

action #108884

closed

Pausing and resuming test skips to next module when using restapi ?

Added by JRivrain over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
2022-03-24
Due date:
% Done:

0%

Estimated time:

Description

Observation

In that case, I was trying to troubleshoot a failure where a specific page is not shown.
So I chose to pause the execution to see what really happens. I saw that the page is effectively not here, so I resumed, expecting the test to fail from that point and collect logs. But it did not, and skipped to next module instead.
We could try to reproduce this, maybe by adding this module to another test suite where the page does not appear, and investigate what is going on.

openQA test in scenario sle-15-SP4-Online-ppc64le-activate_encrypted_volume+force_recompute@ppc64le fails in
activate_encrypted_volume

Test suite description

Maintainer: QE Yast, rpalethorpe

In the current state (as of 2017-01) SLE as well as openSUSE can detect an existing cryptlvm installation and offer to activate it. However, as might be unexpected, the proposed partition layout does not propose an encrypted layout based on this. Only if the cryptlvm layout is selected explicitly it will be encrypted again. This test was added as there was a bug preventing even the recomputation.

Reproducible

Fails since (at least) Build 116.4

Expected result

Last good: 113.1 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by JRivrain over 2 years ago

  • Project changed from openQA Tests (public) to qe-yam
  • Category deleted (Bugs in existing tests)
Actions #2

Updated by JRivrain over 2 years ago

  • Tags set to qe-yast-refinement
Actions #3

Updated by JRivrain over 2 years ago

  • Description updated (diff)
Actions #4

Updated by JERiveraMoya over 2 years ago

Extract from conversation in Slack with Marius and Oliver:

If you tell it to pause on the next command than that really requires a backend command. A test API function which does not invoke a backend command isn't sufficient as well.)
If you tell it to pause on some test module the same limitation applies. The command to set the current test name only let's the developer mode pause before the next command within that test module but if there's none it'll not pause. That's something we could likely improve.
If you want to workaround it, I suppose all test API functions which internally invoke query_isotovideo are sufficient.

https://github.com/os-autoinst/os-autoinst/pull/2007

Actions #5

Updated by JERiveraMoya over 2 years ago

  • Target version set to Current
Actions #6

Updated by JERiveraMoya over 2 years ago

  • Tags deleted (qe-yast-refinement)
  • Subject changed from pausing and resuming test skips to next module when using restapi ? to Pausing and resuming test skips to next module when using restapi ?
  • Status changed from New to Feedback
  • Assignee set to JRivrain

@jonathan will check for the fix in this pause mechanism.

Actions #7

Updated by JRivrain over 2 years ago

  • Status changed from Feedback to Closed

Checked in https://openqa.suse.de/tests/8476255, it paused before the test module as expected, rather than after.

Actions

Also available in: Atom PDF