----- "James Laska" <jlaska(a)redhat.com> wrote:
On Tue, 2010-06-15 at 10:53 +0000, "Jóhann B. Guðmundsson"
wrote:
> On 06/15/2010 10:09 AM, Kamil Paral wrote:
> > PS: If anyone sees any deficiencies in other test cases, feel free
to
> > improve or suggest an improvement.
> >
> >
> WARNING!!! VNC server running with NO PASSWORD!
> You can use the vncpassword=<password> boot option
> if you would like to secure the server.
>
>
> Do we ( should we?) have separate test case to check if setting and
> using the vnc password works?
> ( "User can connect with VNC client with and without having a
password" )
Good suggestion. I'm always worried about getting too many tests
that
we drown in them. Perhaps we have this VNC+passwd test only run once
during a cycle, or we update the test instructions to try *both*
password and password-less operation?
Any preference?
I would add optional clauses to test cases for items that are not
critically important. It is important VNC works, it is not so
important vnc password works. So I would add a clause:
"If you want, you can add option vncpassword=..."
We can't test manually every possible feature.
Also, should we add a step in the 'how to test' to confirm that
modifier
keys work
(
http://fedoraproject.org/wiki/Common_F13_bugs#vnc-modifier-keys)?
I think this is included in the VNC test itself. When we say "VNC
should work" we expect that the user tries standard procedures -
using keyboard included. I wouldn't name everything explicitly,
it's not even possible.
Thanks,
James
--
test mailing list
test(a)lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test