Well.. I was planning to test all installation process, testing all options and after go to desktop test. For installation, I will test automated installation, without changing options, just accepting it, after doing some customization, and after test "experienced" installation. To desktop tests, I will like to test a basic office suite: Desktop with firefox, konqueror, mail clients, and office working, without crashes. I know, which firefox and openoffice, for example, isn't developed by openSUSE Project, but its really important these integration for a workstation. I can test it with gnome and kde. I saw the last email talking about desktop tests too... I think which we can do 2 major teams to testing: Installation and Desktop. There are a lot of choices and ways to install... and maybe bugs too. For desktop? Well... a riot from choices and setup, to test and check. IMHO - I'm thinking about important topics to test Installation Test Team -- Test all installation process: - Test different installation options, until the first installation screen - text or graphical - Languages support: For example, german, english, spanish, portuguese and french. Yes, there's a lot of languages also!; - Keyboard layout support: To test the main layout offered; - Test YaST repositories and hardware detection in the first detection screen; - Test automated installation -- extensive tests. Pay a lot of attention to usability, for final and low experienced users; - Test Partitioner - LVM, ext3, ext4, mounting NFS and FAT32 and NTFS partitions; - Test YaST packager - Choose, solving dependencies.... - Test Security/Auth - Choosing different methods, different passwords and so on; - Test Network Configuration - DHCP, Static IP.... and many different setups; - Test YaST updates; - Test final hardware detection, as VideoCard... - And finally: test the final result after the first GNOME/KDE boot. Desktop Test Team -- Test all desktop(as a workstation/media center/basic server): - Test KDE initial boot and first setup - Test GNOME initial boot and first setup - Test KDE Language support and Keyboard Layout; - Test GNOME Language support and Keyboard Layout; For both: - Test Hardware - Sound, Video, Bluetooth devices; - Test firefox integration; - Test file manager(Nautilus/Dolphin); - Test automount; - Test network configuration; - Test openoffice integration; - Test IM integration; - Test Mail Client integration; We don't need an official desktop or installation test team. We can't decide by ourselves, and choose and area to test and fill bugzilla with our tests, and of course, there are many tests to do which Holger already created! If a team finish desktop or installation tests, can help another team to finish also. Is not a competition, its a better organization for tests and easier to concentrate in a few and exhausted tests. Is it a good idea or not? Sorry, I'm entering just now in testing mailing list, but its my 2 cents of contribution. All the best. 2009/9/10 Gabriel Franco <gffranco@gmail.com>:
2009/9/10 Spencer French <spf@varndean.ac.uk>:
Considering images for m7 should be around now/soon I was wondering what other members of the team thought our plan should be for this far along in the dev cycle?
And also what testing preferences each member has as well as available hardware so we can all have a rough idea of each others work flow.
I have 2 desktop machines both x86/64 as well as a macbook pro (early 2009) and a newish dell laptop, so I can do resume/suspend testing of those models. As far as preference I am really interested in the kde desktop/yast/zypper and xorg, although of course I will help with anything I can.
Also just as a heads up at work I will be posting from spf@varndean.ac.uk and at home from spencerpaulfrench@gmail.com.
Please consider the environment, only print out this email if absolutely necessary This email, together with any attachments, (the document) is for the exclusive use of the addressee(s). Any other distribution, use or reproduction of the document without the sender's prior consent is unauthorised and strictly prohibited. If you have received this document in error please notify the sender, by email or by telephone immediately and remove the message from your computer without making any copies. It is possible for data conveyed by email to be deliberately or accidentally intercepted or corrupted. For this reason, in communicating solely by email, Varndean College is unable to accept any responsibility for any breaches of confidence which may arise through the use of this medium. Varndean College will not accept any liability for contractual commitments made by individuals employed by Varndean College outside the scope of our business. Varndean College, Surrenden Road, Brighton, East Sussex, BN1 6WQ Tel: 01273 508011 Fax: 01273 542950 For further information on Varndean College, please visit our web site at http://www.varndean.ac.uk
-- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org
Hi Spencer,
I have 1 laptop x86/x64, an EeePC 1000h and an Aigo MID P8861H
I think that the first item the Testing team need to come up with is the definition of the main areas we are going to focus for our testing and define sub-teams for each of the areas based on members preferences
I think that we need to come up with a Test Plan / Cases for 2 main scenarios:
- KDE Desktop
- Gnome Desktop
We need to define what to test and how to test the main applications provided on both desktop solutions like browser, e-mail client, file manager, yast, communication (IM and IRC), network management (WI-FI, ETH, PPP, VPN) and so on.
For that we need to analyze what is already available as test cases on testopia and fill up the missing parts.
Maybe we should try setting up a Team Meeting to get to know every member and come up with the first plan and objectives for the team.
What do you think?
Best,
-- Gabriel Fróes Franco Software Architect Zend Certified Engineer - PHP5 Sun Java Certified Programmer - Java 5 openSUSE Member openSUSE Testing Core Team
Discover Freedom
openSUSE Linux http://www.opensuse.org
OpenOffice.org http://www.openoffice.org
Netbeans IDE http://www.netbeans.org
Please consider the environment before printing this e-mail.
To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org
-- /\ Gabriel Stein gabrielstein@gmail.com +55 51 9953 1337 -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org