action #50723
closed
[functional][y] Automate yast2 hostname using libyui-rest-api for tumbleweed
Added by riafarov about 5 years ago.
Updated 3 months ago.
Description
Motivation¶
I, as a QA engineer would like to learn potential issues when running tests using new framework vs needles
Documentation for the framework can be found here: https://github.com/libyui/libyui-rest-api
Idea is to write test for the module which already has automated test and run both for some time and compare efforts for the maintenance and review.
Acceptance criteria¶
- Test for yast2 hostname using libyui-rest-api is running in parallel to screen based test
#50726 should be resolved first, so in case it's not, please, move to the next sprint.
- Due date changed from 2019-06-04 to 2019-06-18
- Blocked by action #50726: [functional][y][timeboxed:16h] Explore different ideas which technologies to use with libyui-rest-api added
- Status changed from New to Blocked
- Assignee set to riafarov
- Due date changed from 2019-06-18 to 2019-07-30
- Target version set to Milestone 27
- Due date changed from 2019-07-30 to 2019-09-24
- Target version changed from Milestone 27 to Milestone 30+
- Due date changed from 2019-09-24 to 2019-10-22
We are getting closer, but not in the next sprint.
- Due date changed from 2019-10-22 to 2019-11-19
- Due date changed from 2019-11-19 to 2020-02-11
- Target version changed from Milestone 30+ to Milestone 30
bulk moved to M30 for revisiting
- Due date changed from 2020-02-11 to 2020-04-07
- Target version changed from Milestone 30 to Milestone 33
- Due date deleted (
2020-04-07)
- Target version changed from Milestone 33 to future
- Project changed from openQA Tests to qe-yam
- Status changed from Blocked to New
- Assignee deleted (
riafarov)
- Priority changed from Normal to Low
- Target version deleted (
future)
- Parent task deleted (
#50672)
- Status changed from New to Rejected
Also available in: Atom
PDF