Difference between revisions of "Talk:SME8.0 QA"

From SME Server
Jump to navigationJump to search
m
 
(2 intermediate revisions by one other user not shown)
Line 5: Line 5:
  
 
~~byte aka Gavin
 
~~byte aka Gavin
 +
=comments=
  
 +
When doing an upgrade we need to know how an upgrade is taking place i.e CD or YUM and we need to test both upgrade paths.
 +
 +
Also don't forget to open separate bugs as their maybe issues with the upgrade as noticed a few talking points in the bug tracker with the /root/upgrade.log
  
 
=Proposed template=
 
=Proposed template=
 
Update this over the next day, then we can copy over to the QA page and sort the comments
 
 
After that if new sections are added in the QA page please update this template so it's ready for beta5, RC1 etc
 
 
Although I'm not sure all the steps need to be repeated for each beta, just start again for the Release Candidate
 
  
 
=Testing=
 
=Testing=
Line 92: Line 90:
 
====Backup x====
 
====Backup x====
  
*to desktop
+
=====to desktop x=====
  
*to tape
+
=====to tape x=====
  
*to workstation
+
=====to workstation x=====
  
*to usb disk
+
=====to usb disk x=====
  
 
====Restore x====
 
====Restore x====
  
*from desktop (command line)
+
=====from desktop (console) x=====
  
*from tape
+
=====from tape x=====
  
*from workstation
+
=====from workstation x=====
  
*from usb disk
+
=====from usb disk x=====
  
 
===View log files x===
 
===View log files x===

Latest revision as of 21:48, 24 September 2009

comments

I feel we need more than a "Pass" as for example under the server roles the PDC test was past but with not much information about what other PDC tests were done for example does PDC pass if you create a domain admins group and try to join a XP client with a user in the domain admins group ?!

Its an excellent start as I've said but we must be sure we are giving as good QA as we can so therefore we must make sure each test is tested intensively and showing that its been tested intensively.

~~byte aka Gavin

comments

When doing an upgrade we need to know how an upgrade is taking place i.e CD or YUM and we need to test both upgrade paths.

Also don't forget to open separate bugs as their maybe issues with the upgrade as noticed a few talking points in the bug tracker with the /root/upgrade.log

Proposed template

Testing

Test guidelines

Installation x

Installation types x

Upgrading x

Upgrade from older versions x

to check: /var/log/messages

  • from 7.4
  • from 7.3
  • from 7.2
  • from 7.1
  • older 7.0


Console x

Check Status x

Configure Server x

DHCP server x

Server-gateway x

Server-only x

Test internet x

Reboot x

Raid x

Access Server Manger x

View Support x

Backup to USB x

Server Manager x

Collaboration x

Users x

Groups x

Quotas x

Pseudonyms x

Information Bays x

User access via file sharing x

Public access via web x

dynamic content

Administration x

Backup and restore x

Backup x

to desktop x
to tape x
to workstation x
to usb disk x

Restore x

from desktop (console) x
from tape x
from workstation x
from usb disk x

View log files x

Mail lof files x

Reboot and shutdown x

Security x

Remote access x

VPN / PPTP x

Remote management x

SSH x

FTP x

Local Networks x

Port forwarding x

Proxy settings x

Mail x

Web x

Configuration x

Software Installer x

Updates x

Settings x

Date and time x

Workgroup x

Domain controller x

Roaming profiles x

Directory x

Printers x

Hostnames x

Domains x

Email x

Access x

Filtering x

Reception x

Delivery x

Antivirus x

Review x

Miscellaneous x

Support x

Starter Website x

Other x

Languages x

Displays ok, translations up-to-date

Danish x

Dutch x

Estonian x

French x

German x

Greek x

Hungarian x

Indonesian x

Italian x

Norwegian x

Portuguese x

Portuguese Brazil x

Romanian x

Russian x

Slovenian x

Spanish x

Swedish x