Project

General

Profile

Actions

coordination #55142

closed

[migration][PjM][saga] Extending Migration testing into functional domains and teams

Added by coolgw over 4 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
New test
Target version:
SUSE QA - Milestone 35+
Start date:
2019-08-06
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

[Gao Wei]:Since i delete 39812 by my mistake, we can using this to continue track.

While QA SLE department has a migration team located in Beijing (part of Sunny's line team), there is an opportunity to collaborate better and thus enhance/extend migration testing.

Why do we talk about this? During SLE15 SP0 migration was problematic area, as:

  • it was defined very late; at first we were acting on poorly communicated and not clear requirements;
  • during SLE15 SP0 some aspects (requirements) of migration were changing which was making automation nearly impossible;
  • finally our testing effort in limited migration team are focused on migration itself including testing RMT/SMT etc.

Our testing of migration is about testing matrix of various migration paths where we check if this process can be accomplished successfully.

Discussed idea with Sunny, Thorsten Kukuk, Marita and number of other people is to now ask functional teams to introduce some migration testing for some "services".
As Thorsten described it: check if certain services can survive migration.

Initial idea:

  • migration functional team is working on testing migration and maintaining all migration openQA modules;
  • each of the functional team should then consider testing some services in the way that they set them up in older system, call migration openQA module and check if configured service survives the migration.

During the talks with Thorsten following services were named as good to test:

  • apache
  • bind
  • net-snmp
  • dhcp server
  • nfs-server
  • rpcbind
  • radvd
  • cron (including all cronjobs, e.g. the in /etc/crontab)
  • apparmor
  • autofs
  • cups
  • kdump
  • ntp/chrony
  • postfix
  • firewall
  • vsftpd

Please note: this is not about asking you to do even more work within the same time. Product Owners should work with Project Manager on priorities, so perhaps some testing could be dropped in order to add some of these migration testing.


Files

Actions

Also available in: Atom PDF