From Fedora Project Wiki
< Architectures | ARM | Quality Assurance
No edit summary |
|||
| Line 2: | Line 2: | ||
==Participants== | ==Participants== | ||
=Tests to be performed= | =Tests to be performed= | ||
==Alpha Release Requirements== | |||
# A correct checksum must be published for each official release image. | |||
# There must be no file conflicts (cases where the files in some packages conflict but the packages have explicit Conflicts: tags are acceptable) or unresolved package dependencies in the released rootfs images | |||
# Starting with the F18-ARM release: In most cases a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation (possibly after automated resizing or other steps, possibly also including a reboot), without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode the system is booted without an interactive user interface (e.g., headless). This includes correctly accessing any encrypted partitions when the correct passphrase is supplied. The firstboot utility must be able to create a working user account, set the root password, and set the timezone and current time. | |||
# Following on from the previous criterion, after firstboot is completed and on subsequent boots, a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to a working graphical environment without unintended user intervention, if graphic hardware and user interface devices (pointer, keyboard) are available. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied | |||
# When booting a system installed without a graphical environment, or when using a correct configuration setting to cause an installed system to boot in non-graphical mode, the system should boot to a state where it is possible to log in through at least one of the default virtual consoles | |||
# It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments. The web browser must be able to download files, load extensions, and log into FAS | |||
# The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops | |||
BUG - must uncheck "only native packages" to get arm packages to show up | |||
# The default Fedora artwork must either refer to the current Fedora release under development (Fedora 17), or reference an interim release milestone (e.g. Alpha or Beta). If a release version number is used, it must match the current Fedora release under development. This includes artwork used in the installer, graphical bootloader menu, firstboot, graphical boot, graphical login and desktop background. | |||
# A system logging infrastructure must be available and enabled by default. It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages. This must be done in accordance with relevant standards accepted by the Project. | |||
# It must be possible to trigger a system shutdown using standard console commands, and the system must shut down in such a way that storage volumes (e.g. simple partitions, LVs and PVs, RAID arrays) are taken offline safely. | |||
=Fedora ARM VFAD - Fedora 17 Test Day Results= | =Fedora ARM VFAD - Fedora 17 Test Day Results= | ||
Revision as of 17:15, 14 June 2012
Fedora ARM VFAD - Fedora 17 Test Day
Participants
Tests to be performed
Alpha Release Requirements
- A correct checksum must be published for each official release image.
- There must be no file conflicts (cases where the files in some packages conflict but the packages have explicit Conflicts: tags are acceptable) or unresolved package dependencies in the released rootfs images
- Starting with the F18-ARM release: In most cases a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation (possibly after automated resizing or other steps, possibly also including a reboot), without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode the system is booted without an interactive user interface (e.g., headless). This includes correctly accessing any encrypted partitions when the correct passphrase is supplied. The firstboot utility must be able to create a working user account, set the root password, and set the timezone and current time.
- Following on from the previous criterion, after firstboot is completed and on subsequent boots, a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to a working graphical environment without unintended user intervention, if graphic hardware and user interface devices (pointer, keyboard) are available. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied
- When booting a system installed without a graphical environment, or when using a correct configuration setting to cause an installed system to boot in non-graphical mode, the system should boot to a state where it is possible to log in through at least one of the default virtual consoles
- It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments. The web browser must be able to download files, load extensions, and log into FAS
- The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops
BUG - must uncheck "only native packages" to get arm packages to show up
- The default Fedora artwork must either refer to the current Fedora release under development (Fedora 17), or reference an interim release milestone (e.g. Alpha or Beta). If a release version number is used, it must match the current Fedora release under development. This includes artwork used in the installer, graphical bootloader menu, firstboot, graphical boot, graphical login and desktop background.
- A system logging infrastructure must be available and enabled by default. It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages. This must be done in accordance with relevant standards accepted by the Project.
- It must be possible to trigger a system shutdown using standard console commands, and the system must shut down in such a way that storage volumes (e.g. simple partitions, LVs and PVs, RAID arrays) are taken offline safely.
Fedora ARM VFAD - Fedora 17 Test Day Results
| Hardware | Who's Testing | item 1 | item 2 | item 3 | item 4 | item 5 |
|---|---|---|---|---|---|---|
| Versatile Express (Qemu) | ||||||
| Versatile Express+XFCE (Qemu) | ||||||
| Pandaboard | ||||||
| Pandaboard+XFCE | ||||||
| Trimslice Bare/Value Pro/H/H250 | ||||||
| Trimslice Pro/H/H250 | ||||||
| Highbank | ||||||
| Beagleboard XM | ||||||
| Kirkwood (sheevaplug, dreamplug, guruplug, etc) | ||||||
| Raspberry Pi+XFCE | ||||||
| Raspberry Pi |