[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Appropriate test priority for telnet and cmdline installs

On Mon, 2010-02-08 at 16:55 -1000, David Cantrell wrote:
> Hash: SHA1
> On Mon, 8 Feb 2010, Chris Lumens wrote:
> >> https://fedoraproject.org/wiki/QA:Testcase_Anaconda_User_Interface_Cmdline
> >>
> >> As I understand it, the cmdline case is important for platforms that
> >> don't support newt console output (e.g. s390x).  However, it's been
> >> leveraged heavily by test automation as it makes for easier to follow
> >> test logs.  This is a lightweight test for us to continue with, so I'd
> >> be comfortable assigning this a priority of Beta.  Thoughts/concerns?
> >
> > Agreed as to the users.  I'm curious why you give this a different
> > priority from serial console, though.  It feels like serial and cmdline
> > have the same set of use cases and should be tested at the same level.
> Serial console installs can still be interactive, whereas the cmdline mode
> requires a kickstart file and is really just a progress indicator (right?).
> Despite being named cmdline mode, I'm pretty sure it's not at all interactive.

That's my understanding.  David, you probably know better than me, but
since prompting on a 3270 console isn't an option, all cmdline installs
should not be interactive.


Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]