From Fedora Project Wiki

No edit summary
(Minor organizational tweaks)
Line 7: Line 7:
|}
|}


=== What to test? ===
= What to test? =


Today's installment of Fedora Test Day will focus on '''NFS'''
Today's installment of Fedora Test Day will focus on '''NFS'''


=== Who's available ===  
= Who's available =


The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
Line 17: Line 17:
* Quality Assurance - [[User:caiqian]]
* Quality Assurance - [[User:caiqian]]


=== Prerequisite for Test Day ===  
= What's needed to test =


* desire to break software
* A system with some kind of network connection
* CD/DVD-ROM or Rawhide Fully updated
* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]
* update the following packages on a F12 box,
* An installed Fedora distribution, either:
** [[Releases/Rawhide|Rawhide]] or the live CD available for this test day
** Or an previously installed {{FedoraVersion|long|12}} system (see [[http://docs.fedoraproject.org/install-guide/f{{FedoraVersion|12}} Installation guide])


kernel ->2.6.33-0.24.rc5.git1.fc13
= How to test? =


nfs-utils ->nfs-utils-1.2.1-16.fc13
== Rawhide ==


make sure 'Defaultvers=3' variable is disabled in /etc/nfsmount.conf.
If testing using [[Releases/Rawhide|Rawhide]], you may
# '''Install''' latest rawhide from a local mirror. Please follow this guidance to use rawhide -- [[Releases/Rawhide#Direct_Rawhide_install|Install from a nearby rawhide mirror]].
# Or, '''update''' to rawhide from {{FedoraVersion|long}}.  For guidance, refer to [[Releases/Rawhide#Yum_update_from_official_release]]
# Alternatively, you may download a non-destructive rawhide '''live image''' for your architecture. Tips on using a live image are available at [[FedoraLiveCD]].  Live images can be found at http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop .


== Fedora 12 ==


=== How to test? ===
Testing can be also be performed on Fedora 12 system with only a few changes.
# First, update the {{package|kernel}} package to kernel-2.6.33-0.24.rc5.git1.fc13 or newer
# Next, update the {{package|nfs-utils}} package to nfs-utils-1.2.1-16.fc13 or newer
# Lastly, update {{filename|/etc/nfsmount.conf}} and comment out the line that reads <pre>Defaultvers=3</pre>


Basically, this can be tested with both server and client on the same machine, and with different bare-metal or virtual systems. It will need to setup a NFS server, and run some automated NFS testsuites for it from clients. In addition, we will use generic filesystem testsuites to exercise NFS filesystem. An important part of the test event is to make sure everything is working properly after we have switched to [[Features/NFSv4Default|NFSv4 by default in Fedora 13]].
= Test Cases =


Also, we will test Secure NFS as well. All the results will be reported to the table below.
Basically, NFS can be tested with both server and client on the same machine, and with different bare-metal or virtual systems. Testers will need to setup a NFS server, and run automated NFS testsuites from client systems.  In addition, we will use generic filesystem testsuites to exercise NFS filesystem integrity. An important part of the test event is to make sure everything is working properly after we have switched to [[Features/NFSv4Default|NFSv4 by default in Fedora 13]].


=== Test Cases ===
Also, we will test Secure NFS.  All the results will be reported to the table below.


# [[QA:Testcase_nfs_connectathon]]
# [[QA:Testcase_nfs_connectathon]]
Line 45: Line 54:
# [[QA:Testcase_nfs_generic_secure]]
# [[QA:Testcase_nfs_generic_secure]]


=== Test Results ===
= Test Results =


Construct a table or list to allow testers to post results.  Each column should be a test case or configuration, and each row should consist of test results.  For example:
Construct a table or list to allow testers to post results.  Each column should be a test case or configuration, and each row should consist of test results.  For example:

Revision as of 15:44, 28 January 2010

DATE TIME WHERE
NFS From 12:00 to 21:00 UTC (8am -> 5pm EDT) #fedora-test-day (webirc)

What to test?

Today's installment of Fedora Test Day will focus on NFS

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

What's needed to test

  • A system with some kind of network connection
  • Your hardware profile uploaded to Smolt according to these instructions
  • An installed Fedora distribution, either:

How to test?

Rawhide

If testing using Rawhide, you may

  1. Install latest rawhide from a local mirror. Please follow this guidance to use rawhide -- Install from a nearby rawhide mirror.
  2. Or, update to rawhide from Fedora 40. For guidance, refer to Releases/Rawhide#Yum_update_from_official_release
  3. Alternatively, you may download a non-destructive rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found at http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop .

Fedora 12

Testing can be also be performed on Fedora 12 system with only a few changes.

  1. First, update the Package-x-generic-16.pngkernel package to kernel-2.6.33-0.24.rc5.git1.fc13 or newer
  2. Next, update the Package-x-generic-16.pngnfs-utils package to nfs-utils-1.2.1-16.fc13 or newer
  3. Lastly, update /etc/nfsmount.conf and comment out the line that reads
    Defaultvers=3

Test Cases

Basically, NFS can be tested with both server and client on the same machine, and with different bare-metal or virtual systems. Testers will need to setup a NFS server, and run automated NFS testsuites from client systems. In addition, we will use generic filesystem testsuites to exercise NFS filesystem integrity. An important part of the test event is to make sure everything is working properly after we have switched to NFSv4 by default in Fedora 13.

Also, we will test Secure NFS. All the results will be reported to the table below.

  1. QA:Testcase_nfs_connectathon
  2. QA:Testcase_nfs_pynfs
  3. QA:Testcase_nfs_generic
  4. QA:Testcase_nfs_connectathon_secure
  5. QA:Testcase_nfs_pynfs_secure
  6. QA:Testcase_nfs_generic_secure

Test Results

Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. For example:

User Smolt Profile connectathon pynfs generic-fs connectathon secure pynfs secure generic-fs secure References
User:caiqian HW PASS PASS FAIL [1] PASS PASS PASS
  1. See RHBZ #12345