Alan provided additional input for the proposed new shutdown test. I
have updated the document and attached it.
This test case
(https://fedoraproject.org/wiki/QA:Testcase_base_shutdown/reboot) does
not seem to be in the Base test matrix anymore. We should consider
adding it back to the
On 1/11/19 5:08 PM, Alan Jenkins wrote:
On 11/01/2019, pmkel...@frontier.com wrote:
https://fedoraproject.org/wiki/QA:Testcase_base_shutdown/reboot
Basically:
1. On a running system, change to a virtual console by pressing
Ctrl+Alt+F2
2. At the virtual console, login as the root
On 11/01/2019, pmkel...@frontier.com wrote:
>> https://fedoraproject.org/wiki/QA:Testcase_base_shutdown/reboot
>>
>> Basically:
>>
>> 1. On a running system, change to a virtual console by pressing
>> Ctrl+Alt+F2
>> 2. At the virtual console, login as the root user
>> +3. Halt the system by
On 11/01/2019, pmkel...@frontier.com wrote:
>
> On 1/11/19 7:26 AM, Alan Jenkins wrote:
>> Hi QA people!
>>
>> In the past few years I've seen four shutdown bugs. The problem is that
>> the screen turns off too quickly, so even if it shows error messages, most
>> people don't actually see them.
Thanks for these! They look good and the formatted tests will make adding
them a lot easier. I have opened an issue on the QA pagure page [0] and
will plan to bring this up at the next QA meeting. Please attend if you can
as your perspective will help us all make a decision!
[0]
On 1/11/19 7:26 AM, Alan Jenkins wrote:
Hi QA people!
In the past few years I've seen four shutdown bugs. The problem is that the
screen turns off too quickly, so even if it shows error messages, most people
don't actually see them. Or at least, it requires extra effort if you want to
Hi QA people!
In the past few years I've seen four shutdown bugs. The problem is that the
screen turns off too quickly, so even if it shows error messages, most people
don't actually see them. Or at least, it requires extra effort if you want to
report them.
At least three of the four
