Project

General

Profile

Actions

coordination #44054

closed

[functional][y][epic] Develop maintainable and scalable test framework

Added by oorlov over 5 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 25
Start date:
2018-11-20
Due date:
2019-05-21
% Done:

100%

Estimated time:
(Total: 24.00 h)
Difficulty:

Description

As an QA Automation Engineer
I want to have maintainable and scalable test framework,
So that I'll be able to create new tests and update the existing ones:

  • Without having to keep all the product versions in mind to not cause regression after each change;
  • Avoiding code duplications.

Subtasks 4 (0 open4 closed)

action #44057: [functional][y][timebox:20h] Design prototype for the testing framework using object oriented/functional approachResolvedoorlov2018-11-202018-12-04

Actions
action #44753: [functional][y] Refactor partitioning_lvm test module using new framework designResolvedoorlov2018-12-052019-02-12

Actions
action #46676: [functional][y] Refactor yast2 test modules structure and namingsResolvedybonatakis2019-01-242019-05-21

Actions
action #46766: [functional][y] Add documentation for the UI test framework with the new approachResolvedoorlov2019-01-282019-04-09

Actions

Related issues 1 (0 open1 closed)

Related to openQA Tests - action #45116: [functional][y] Try to find better names for version control functions instead of e.g. "is_storage_ng_newui"Rejectedriafarov2018-12-13

Actions
Actions #1

Updated by okurz over 5 years ago

  • Description updated (diff)
  • Target version set to Milestone 24

@zluo I assume this ticket is the one you were looking for when you mentioned "branches"

Actions #2

Updated by okurz over 5 years ago

  • Related to action #45116: [functional][y] Try to find better names for version control functions instead of e.g. "is_storage_ng_newui" added
Actions #3

Updated by riafarov over 5 years ago

  • Due date changed from 2018-12-18 to 2019-01-15

due to changes in a related task

Actions #4

Updated by okurz over 5 years ago

  • Status changed from New to Blocked
  • Assignee set to okurz

to track the subtasks

Actions #5

Updated by riafarov over 5 years ago

  • Due date changed from 2019-01-15 to 2019-01-29

due to changes in a related task

Actions #6

Updated by oorlov over 5 years ago

  • Due date changed from 2019-01-29 to 2019-02-12

due to changes in a related task

Actions #7

Updated by riafarov about 5 years ago

  • Due date changed from 2019-02-12 to 2019-02-26

due to changes in a related task

Actions #8

Updated by riafarov about 5 years ago

  • Due date changed from 2019-02-26 to 2019-03-12

due to changes in a related task

Actions #9

Updated by riafarov about 5 years ago

  • Due date changed from 2019-03-12 to 2019-03-26

due to changes in a related task

Actions #10

Updated by okurz about 5 years ago

  • Assignee changed from okurz to riafarov

to track as stand-in as discussed

Actions #11

Updated by oorlov about 5 years ago

  • Due date changed from 2019-03-26 to 2019-04-09

due to changes in a related task

Actions #12

Updated by riafarov about 5 years ago

  • Status changed from Blocked to In Progress
Actions #13

Updated by riafarov about 5 years ago

  • Due date changed from 2019-04-09 to 2019-04-23

due to changes in a related task

Actions #14

Updated by riafarov about 5 years ago

  • Due date changed from 2019-04-23 to 2019-05-07

due to changes in a related task

Actions #15

Updated by JERiveraMoya almost 5 years ago

  • Due date changed from 2019-05-07 to 2019-05-21

due to changes in a related task

Actions #16

Updated by mgriessmeier almost 5 years ago

  • Target version changed from Milestone 24 to Milestone 25
Actions #17

Updated by riafarov almost 5 years ago

  • Status changed from In Progress to Resolved

This is finally done. Kudos to the team!

Actions #18

Updated by szarate over 3 years ago

  • Tracker changed from action to coordination
Actions

Also available in: Atom PDF