action #28988
open[qe-core][sle][functional] modify or drop scripted_run_slow function since it makes test module not fail on error
0%
Description
As observed from a test module zypper_lr_validation for SLE15 that although there were errors in the result from the command, the test module didn't register or show as failed. This may lead to the fact that we overlook serious issues. And the reason why it happened was that the command run_scripted_command_slow($cmd, slow_type => 2); didn't throw exception as one had expected, since it only calls type_string_very_slow and wait_serial but not assert_script_run.
acceptance criteria¶
- AC1: Modify (or drop) run_scripted_command_slow function so that a test module dies if the command didn't return zero.
tasks¶
- Modify or drop run_scripted_command_slow function
- Make sure the modules that called run_scripted_command_slow function still work afterwards
Updated by Anonymous over 6 years ago
- Related to action #25450: [sle][functional][medium] test fails in zypper_lr_validate added
Updated by okurz over 6 years ago
- Project changed from 46 to openQA Tests
- Category set to Enhancement to existing tests
- Target version set to Milestone 14
Updated by okurz about 6 years ago
- Due date set to 2018-03-27
- Target version changed from Milestone 14 to Milestone 15
Updated by okurz about 6 years ago
- Due date deleted (
2018-03-27) - Target version changed from Milestone 15 to Milestone 17
sprint13 too full, just as well as M15 and M16
Updated by okurz almost 6 years ago
- Subject changed from [sle][functional]modify or drop scripted_run_slow function since it makes test module not fail on error to [sle][functional] modify or drop scripted_run_slow function since it makes test module not fail on error
- Target version changed from Milestone 17 to Milestone 21+
Updated by okurz almost 6 years ago
- Target version changed from Milestone 21+ to Milestone 21+
Updated by okurz over 5 years ago
- Subject changed from [sle][functional] modify or drop scripted_run_slow function since it makes test module not fail on error to [sle][functional][u] modify or drop scripted_run_slow function since it makes test module not fail on error
Updated by okurz over 5 years ago
- Target version changed from Milestone 21+ to future
Updated by szarate about 4 years ago
- Status changed from New to Workable
- Priority changed from Normal to High
- Target version changed from future to Milestone 30
- Estimated time set to 42.00 h
Replace run_scripted_command_slow with assert_script_run
Updated by jorauch about 4 years ago
- Blocked by action #64806: [qe-core][functional] Implement slow_type parameter for assert_script_run added
Updated by jorauch about 4 years ago
- Status changed from Workable to Blocked
we need an adequate replacement first:
https://progress.opensuse.org/issues/64806
Updated by jorauch about 4 years ago
We only have one usage of this function (in tests/console/zypper_lr_validate.pm) so we decided to drop it completely and replace it with assert_script_run as soon as we have the slow typing feature there
Updated by tjyrinki_suse over 3 years ago
- Subject changed from [sle][functional][u] modify or drop scripted_run_slow function since it makes test module not fail on error to [qe-core][sle][functional] modify or drop scripted_run_slow function since it makes test module not fail on error
Updated by okurz over 2 years ago
- Priority changed from High to Normal
This ticket was set to "High" priority but was not updated within 120 days which is 4 times the period of the SLO for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . The ticket will be set to the next lower priority of "Normal".
Updated by slo-gin over 1 year ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by slo-gin about 1 month ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.