action #103917
closedImprove error message when a test suite is not using client libyui-rest-api.
Description
Motivation
Improve error message when a test suite is not using client libyui-rest-api.
Example of failure: https://openqa.opensuse.org/tests/2082968/modules/disable_online_repos/steps/2
where reviewers don't know exactly why some screen doesn't appear.
AC1: solution should take into account that we run code with lib/DistributionProvider.pm using REST API but also using needling (meaning it might be tricky do the change that level, because it has to work in both ways)
AC2: Failure should be clear for any test module schedule that is using libyui-rest-api but the test suite is not configured for it.
Suggestion
In lib/YuiRestClient.pm
we have:
sub get_app {
my (%args) = @_;
$app = init_app(%args) unless $app;
return $app;
}
which we run for each controller using REST API, here we could use is_libyui_rest_api
with a descriptive error.
Updated by JERiveraMoya almost 3 years ago
- Tags set to qe-yast-refinement
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests) - Priority changed from Normal to High
- Target version set to Current
Updated by JERiveraMoya almost 3 years ago
- Tags deleted (
qe-yast-refinement) - Status changed from New to Workable
Updated by geor over 2 years ago
- Status changed from Workable to In Progress
- Assignee set to geor
Updated by geor over 2 years ago
- Status changed from In Progress to Closed