Mailinglist Archive: opensuse-testing (17 mails)

["Bernhard M. Wiedemann" <bernhardout@xxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi folks,

I found a nice page about the different kinds of testing, that a testing
team like ours should do:

https://wiki.ubuntu.com/Testing/Activities


1. ISO Testing
_before_ milestones to make sure that openSUSE-MS.ISOs are not utterly
broken, making them testable to the general public.
I am not sure if testopia installation test plan can be used for this,
as it wants "releases" like MS3 or RC1 for testing. Maybe we could use
daily builds like "0042" as "release" for testing as well.

2. Daily Factory testing
on VM or spare hardware

3. Stable Release Update (SRU) Testing
to make it less likely that updates break things. Currently done via
bugzilla - e.g. https://bugzilla.novell.com/show_bug.cgi?id=555569#c8
and probably within novell for security-updates

4. Feature Testing
is probably what we did with testopia feature test plan

5. General Testing
we did this anyway with many MS and RC releases, but I must admit that I
did not use every feature as I would on a production system. Possibly
because of other annoying bugs. And I did not report every issue as it
were so many and it takes time searching for dups or writing a good
report. And I only have 20 votes.

6. Application Testing
is probably what we did with testopia's application test plan

7. Automated Testing
to be done


Ciao
Bernhard M.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

iEYEARECAAYFAks9peMACgkQSTYLOx37oWQb2wCgms+Wqd4/Eug7CZpTfJSP9fUL
UWoAoNSbtQd4lFX2cemSaKXlM9bAqDPr
=qVmy
-----END PGP SIGNATURE-----
-- 
To unsubscribe, e-mail: opensuse-testing+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-testing+help@xxxxxxxxxxxx