On Fri, Feb 12, 2021 at 2:28 PM Lukas Ruzicka <lruzicka(a)redhat.com> wrote:
"This test case can be performed on both bare machines." doesn't make
sense
to me.
"Boot the system and log in as a common user." - I think the more
frequently used term is a "regular user". Do I understand correctly that
you mean any non-root user (i.e. your regular user can have admin
privileges - be in the wheel group, right?). Perhaps you can clarify with
"log in as a regular user (i.e. not root)" or similar.
I really really really dislike when there's a testing step "Run command X",
but the step doesn't say what the output should be. And you have to look at
the bottom and try to figure out where it is in the Expected results
section. And basically piece together the actual steps by jumping forth and
back, easily making mistakes or skipping something. The Expected results
section should contain some overall guidance that is valid for the whole
testcase duration, or instructions which don't fit into the testing
structure. But immediate result checking should be part of the How to test
section. For example:
"Check that the pipewire systemd service shows up as active: $ systemctl
--user status pipewire"
or
"Run "pactl list" and verify that is lists all available audio and video
devices on the system"
"the server name must read PulseAudio (on PipeWire \ldots )" - that's some
forgotten formatting in there, I guess?
Could you please rewrite the rest of the testcases into a more readable
format (regarding the "Expected results" section) before I review them all?
Just by quickly looking at them, some of them are very hard to follow,
especially when they commonly have 8+ points in the expected results, and
my brain hurts when trying to make sense of them in this format. I would
get discouraged from executing these test cases just on this ground alone
:-) Thanks a lot.