From Fedora Project Wiki
Fedora Test Days
Echo-testing-48px.png
ARM Test Day

Date 2014-09-18
Time all day

Website QA/Fedora_21_test_days
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

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

Who's available

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

Prerequisite for Test Day

  • MicroSD, SD (SATA HD optional)
  • Supported ARM board (those without hardware can use QEMU to assist with testing)
  • Free space on HD
  • Todays Fedora 21 Candidate image : Disk Images

How to test?

Download a disk image from Koji, and write to media. Existing instructions for supported hardware can be found at on the Fedora Wiki . After writing the disk image and U-Boot test basic functionality including:

  • Network - test wired and wireless connectivity.
  • Storage - test all storage options, minimally USB.
  • Display - test all available display options.

Test Cases

Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see Category:Test_Cases.

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. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:

If you have problems with any of the tests, report a bug to Bugzilla usually for the component udisks, or gnome-disk-utility for bugs in the Palimpsest graphical front end itself. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the result template to enter your result, as shown in the example result line.

Primary

Board User Sample test 1 Sample test 2 Sample test 3 Sample test 4 References
Example Board Sample User
none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345
Utilite Sample User
none
none
none
none
Cubox-i Sample User
none
none
none
none
Hummingboard Sample User
none
none
none
none
RIoTBoard Sample User
none
none
none
none
BeagleBone-Black Sample User
none
none
none
none
PandaBoard Sample User
none
none
none
none
Tegra-K1-Jetson Sample User
none
none
none
none
Trimslice Sample User
none
none
none
none
CubieBoard Sample User
none
none
none
none
Banana-Pi Sample User
none
none
none
none
VExpress Sample User
none
none
none
none

Secondary

Board User Sample test 1 Sample test 2 Sample test 3 Sample test 4 References
BeagleBone-White Sample User
none
none
none
none
Beagle-xM Sample User
none
none
none
none
Novena Sample User
none
none
none
none
UDOO Sample User
none
none
none
none
AC100 Sample User
none
none
none
none
Qualcomm-(IFC6410,DragonBoard) Sample User
none
none
none
none