From Fedora Project Wiki

(Added some test guidance from dcantrell)
(Drop direct Test Days category membership)
 
(38 intermediate revisions by 5 users not shown)
Line 35: Line 35:
#* Alternatively, on an already installed system:
#* Alternatively, on an already installed system:
#*# Install snake: <pre>yum install snake</pre>
#*# Install snake: <pre>yum install snake</pre>
#*# Configure your system for installation: <pre>snake-install http://download.fedora.redhat.com/pub/fedora/linux/releases/test/10-Beta/i386/os</pre>
#*# Configure your system for installation: <pre>snake-install http://download.fedora.redhat.com/pub/fedora/linux/releases/test/10-Beta/Fedora/i386/os</pre>


=== How to test? ===
=== How to test? ===


A wiki test results page for Live Images is in progress.  Once completed, please add your findings and discuss any issues or concerns on IRC #fedora-qa.
Please add your findings to the matrix below or discuss any issues or concerns on IRC #fedora-qa.


Test anaconda networking boot parameters (details at [[Anaconda/Options]]):
'''Assumptions:'''
* ksdevice=
* Do not change ipv6 settings, the default "Auto discovery" should work
* ks=
* All networking configuration (static or dhcp) is done manually, unless specified in the '''boot argument''' column
* ip=


Test that networking data results match when doing graphical and/or text installs:
* static IP
* dynamic IP
* ipv6?


Test network-based installs when booting from:
* boot.iso ([http://download.fedora.redhat.com/pub/fedora/linux/releases/test/10-Beta/Fedora/i386/os/images/boot.iso|i386 boot.iso], [http://download.fedora.redhat.com/pub/fedora/linux/releases/test/10-Beta/Fedora/x86_64/os/images/boot.iso|x86_64 boot.iso)
* PXE


When booting a system via PXE:
{|
* networking is brought up in stage 1 and the source should be found just fine in stage 2
! !! colspan="2"|netboot || colspan="2"|boot.iso
|+The following test matrix was developed by [[User:Dcantrel]]
|-
! Boot argument !! dhcp !! static !! dhcp !! static
|-
| colspan="5" style="background-color: #def3fe;"| Network device selection parameters
|-
| ksdevice=eth0
|style="background-color:lightgreen;"|(johannbg) works
|style="background-color:red;"|(jlaska)[[rhbug:465285|465285]]
Must disable ipv6
|style="background-color:lightgreen;"|(dcantrell) works
|style="background-color:red;"|(jlaska)[[rhbug:465285|465285]]
Must disable ipv6
|-
| ksdevice=MACADDR
|style="background-color:lightgreen;"|(jlaska) works
|style="background-color:red;"|(jlaska)[[rhbug:465285|465285]]
Must disable ipv6
|style="background-color:lightgreen;"|(dcantrell) works
|style="background-color:red;"|(jlaska)[[rhbug:465285|465285]]
Must disable ipv6
|-
| ksdevice=link
|style="background-color:lightgreen;"|(jlaska) works
|style="background-color:red;"|(jlaska)[[rhbug:465285|465285]]
Must disable ipv6
|
|
|-
| ksdevice=BOOTIF
|style="background-color:lightgreen;"|(jlaska) works
|style="background-color:red;"|(jlaska)[[rhbug:465285|465285]]
Must disable ipv6
|
|
|-
| colspan="5" style="background-color: #def3fe;"| Network device configuration parameters
|-
| ip=X.X.X.X
(also includes gateway=, dns= and netmask=)
| colspan="2" style="background-color:red;"|(jlaska)(johannbg)[[rhbug:465270|465270]]
| colspan="2" |
|-
| ip=dhcp
| colspan="2" style="background-color:lightgreen;"|(johannbg) works
| colspan="2" |
|-
| colspan="5" style="background-color: #def3fe;"| Other parameters that require an active network connection
|-
| ks=URL
|style="background-color:red;"|(jlaska)[[rhbug:465314|465314]]
|style="background-color:red;"|(jlaska)[[rhbug:465314|465314]]
|style="background-color:red;"|(jlaska) similar to [[rhbug:465314|465314]] ...
but next starts tui loader screen
|
|-
| updates=URL
|style="background-color:lightgreen;"|(jlaska) works
|style="background-color:red;"|(jlaska)[[rhbug:465285|465285]]
Must disable ipv6
|style="background-color:lightgreen;"|(jlaska) works
|style="background-color:red;"|(jlaska)[[rhbug:465285|465285]]
Must disable ipv6
|-
| repo=URL
|style="background-color:lightgreen;"|(jlaska) works
|style="background-color:red;"|(jlaska)[[rhbug:465285|465285]]
Must disable ipv6
|
|
|-
|}


When booting via a boot.iso,
=== Where to file bugs ===
* networking isn't brought up until stage 2. 


Does ''updates='' auto select networking or prompt?
Please record any issues/defects discovered in Red Hat's [[Bugzilla]].


Does ''ks='' prompt for networking or auto select the "right" network?
* To file a '''NEW''' bug, go to https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&cf_qa_whiteboard=FedoraTestDay
 
* ''Existing'' Test Day bugs can be found at http://tinyurl.com/53thap


=== Need help? ===
=== Need help? ===
Line 70: Line 135:


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 ...
* Development - [[User:dcantrell]], [[User:clumens]]
* Development - [[User:Dcantrel]], [[User:clumens]]
* Quality Assurance - [[User:Johannbg]], [[User:jlaska]], [[User:wwoods]]
* Quality Assurance - [[User:Johannbg]], [[User:jlaska]], [[User:wwoods]]


{{admon/tip|Want to join in?|If you'd like to sign up to help field questions, please add your name to the list above.}}
{{admon/tip|Want to join in?|If you'd like to sign up to help field questions, please add your name to the list above.}}
[[Category:Fedora 10 Test Days]]

Latest revision as of 19:45, 26 June 2015

DATE TIME WHERE
Thu October 2, 2008 From 12:00 to 21:00 UTC (8am -> 5pm EDT) #fedora-qa (need irc help?)

How to join?[edit]

For information on joining a Fedora Test Day, see QA/Test_Days#Where_are_Test_Days_held.3F

What to test?[edit]

This week's instalment of Fedora Test Day will focus on:

Preparing for Test Day[edit]

Depending on the speed of your connection and the time available for testing, there are several methods available for

Live Images

  1. Please download a live ISO image for your architecture:
  2. Prepare your live image by following the instructions at FedoraLiveCD
  3. Or run the dowloaded ISO image in qemu:
     su -c 'qemu -cdrom Fedora-10-Beta-i686-Live.iso -m 512 -std-vga'

Install Media

  1. Consult the installation guide for quick start information to determine the best install method for your needs.
  2. Follow instructions for installing your system.
    • Alternatively, on an already installed system:
      1. Install snake:
        yum install snake
      2. Configure your system for installation:
        snake-install http://download.fedora.redhat.com/pub/fedora/linux/releases/test/10-Beta/Fedora/i386/os

How to test?[edit]

Please add your findings to the matrix below or discuss any issues or concerns on IRC #fedora-qa.

Assumptions:

  • Do not change ipv6 settings, the default "Auto discovery" should work
  • All networking configuration (static or dhcp) is done manually, unless specified in the boot argument column


netboot boot.iso
The following test matrix was developed by User:Dcantrel
Boot argument dhcp static dhcp static
Network device selection parameters
ksdevice=eth0 (johannbg) works (jlaska)465285

Must disable ipv6

(dcantrell) works (jlaska)465285

Must disable ipv6

ksdevice=MACADDR (jlaska) works (jlaska)465285

Must disable ipv6

(dcantrell) works (jlaska)465285

Must disable ipv6

ksdevice=link (jlaska) works (jlaska)465285

Must disable ipv6

ksdevice=BOOTIF (jlaska) works (jlaska)465285

Must disable ipv6

Network device configuration parameters
ip=X.X.X.X

(also includes gateway=, dns= and netmask=)

(jlaska)(johannbg)465270
ip=dhcp (johannbg) works
Other parameters that require an active network connection
ks=URL (jlaska)465314 (jlaska)465314 (jlaska) similar to 465314 ...

but next starts tui loader screen

updates=URL (jlaska) works (jlaska)465285

Must disable ipv6

(jlaska) works (jlaska)465285

Must disable ipv6

repo=URL (jlaska) works (jlaska)465285

Must disable ipv6

Where to file bugs[edit]

Please record any issues/defects discovered in Red Hat's Bugzilla.

Need help?[edit]

We'll have a host of QA and Development characters hanging out discussing bugs (aka "features"), expectations, and test areas. I've included details below for how you can contribute below.

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

Want to join in?
If you'd like to sign up to help field questions, please add your name to the list above.