Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adjust RAID test for storage ng #3548

Merged
merged 1 commit into from Sep 13, 2017

Conversation

rwx788
Copy link
Member

@rwx788 rwx788 commented Sep 8, 2017

Functionality still doesn't fully work, but with this change we will
fail at the point where there is a bug. I've introduced changes to
proceed using different format for disk size, but if fails later because
custom size doesn't work still.

Please, do not forget to merge NEEDLES

See poo#23340.
Verification runs:
SLE15
SLE12SP3

@@ -57,16 +57,16 @@ sub addpart {
send_key "alt-a"; # Raw Volume
send_key $cmd{next};
assert_screen 'partition-format';
send_key $cmd{donotformat};
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not update the hotkey table?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because for non-storage ng key is still valid.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not stupid. But can you define hotkeys based on is_storage_ng and use that with a proper name instead of hard-coding it here?

I see two benefits of the hotkey table:

  • Simplifies setup of an openQA test based on a different INSTLANG setting which we want to have eventually
  • Provides helpful names for the variables instead of a comment

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you saw the code, we recognize if it's storage ng or not in partitioning test module, so we cannot define it before the execution. But possibly we can redefine them in that module, yes. So the only advantage will be hard-coding all keys in one place which may make it even more confusing.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately I have only a single key which has same functionality, but different shortcut in storage-ng, so these changes are introduced in partitioning.pm test module which is executed before and defines STORAGE_NG variable dynamically.


assert_screen 'custompart_systemview-selected';
send_key "down";
assert_screen 'partitioning_raid-hard_disks-selected';



Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed, thanks.

Functionality still doesn't fully work, but with this change we will
fail at the point where there is a bug. I've introduced changes to
proceed using different format for disk size, but if fails later because
custom size doesn't work still.

See poo#23340.
@okurz okurz merged commit 18814f6 into os-autoinst:master Sep 13, 2017
@rwx788 rwx788 deleted the 23340_storage_ng_raid0 branch October 6, 2017 07:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants