== Testing ==
== Testing ==
| || |
== Basic === |+|
=tests , on .
|−|Elementary functionality tests, which should pass on supported GPU. | |
| || |
|−|* [[QA:Testcase_radeon_basic|Boot]] |+|
time to complete, or -
|−|* [[QA:Testcase_radeon_vt|Virtual Terminal]] | |
|−|* [[QA:Testcase_radeon_restartx|X restart]] | |
|−|* [[QA:Testcase_radeon_rendercheck|Rendercheck]] (can take some time to complete, from 10 minutes to an hour or two) | |
|−|* [[QA:Testcase_radeon_glx|GLX]] | |
|−|* [[QA:Testcase_radeon_3D_mesa- demos|Mesa demos]] | |
|−|* [[QA:Testcase_radeon_suspend|Suspend]] | |
| || |
Desktop === |+|
===, on .
|−|Basic desktop usage scenarios, which should pass on supported GPU. | |
| || |
|−|* [[QA:Testcase_radeon_gnome3|Gnome Shell]] |+|
Desktop. Videovideo playbackmay not . 3D may is not yet . , rendering issues and glitches bugreports are more important then performance issues. Experimental'' tests more and .
|−|* [[QA:Testcase KDE4 Desktop Effects|KDE 4]] | |
|−|* [[QA:Testcase_radeon_rotate|Screen rotation]] | |
|−|* [[QA:Testcase_radeon_fastuserswitch|User switch]] | |
|−|* [[QA:Testcase_radeon_multihead|Multihead]] You will need two or more monitors to perform the multihead test. | |
|−|=== Video === | |
|−|Tests focused on different video playback acceleration features. Some older GPUs may not support XvBA. | |
|−|* [[QA:Testcase_radeon_xv|XVideo]] | |
|−|* [[QA:Testcase_radeon_xvmc|XVMC]] | |
|−|* [[QA:Testcase_radeon_vaapi|XvBA]] | |
|−|=== 3D applications/Games === | |
|−|Following applications has been carefully selected to test and exploit various OpenGL features using different rendering engines. If one applications test fails, next may work. Working HW 3D acceleration is needed. | |
|−|* [[QA:Testcase_radeon_3D_pymol|PyMOL]] | |
|−|* [[QA:Testcase_radeon_3D_Stellarium|Stellarium]] | |
|−|<!-- * [[QA:Testcase_radeon_3D_Blender|Blender]] Yo Frankie! is a good candidate for demo, but not in repository yet , more games/demos: http://www.blendergames.org/forum/viewforum. php?f=8&sid=a1d5357c745f3af142fc56410242afa7 --> | |
|−|<!-- * [[QA:Testcase_radeon_3D_tuxracer|Tux Racer]] replaced by SuperTuxKart --> | |
|−|* [[QA:Testcase_radeon_3D_SuperTuxKart|SuperTuxKart]] | |
|−|<!-- * [[QA:Testcase_radeon_3D_openarena|OpenArena]] replaced by Xonotic --> | |
|−|* [[QA:Testcase_radeon_3D_Xonotic|Xonotic]] | |
|−|* [[QA:Testcase_radeon_3D_VDrift|VDrift]] | |
|−|* [[QA:Testcase_radeon_3D_0_A.D.|0 A.D.]] | |
|−|Please file bugs for any failures you find if running these tests. But remember, crashes, rendering issues and glitches bugreports are more important then performance issues. Use your common sense and your knowledge about your GPU limits before reporting performance issues. | |
|−|=== Experimental === | |
|−|Some recommended test cases for people, who likes trying new technology (Wayland, OpenCL) or who are interested in particular scenarios, eg. Steam, Wine. | |
|−|* [[QA:Testcase_vga_switcheroo|Hybrid graphics]] You will need a laptop with two GPUs. Intel and ATI (PowerXpress) or Intel and nVidia (Optimus). | |
|−|* [[QA:Testcase_radeon_3D_Steam|Steam]] | |
|−|<!--* [[QA:Testcase_radeon_3D_Phoronix_Test_Suite|Phoronix Test Suite]]--> | |
|−|<!--* [[QA:Testcase_radeon_Wayland|Wayland]]--> <!-- future test: http://www.phoronix.com/scan.php?page=news_item&px=MTE0NzI --> | |
|−|<!--* [[QA:Testcase_radeon_OpenCL|OpenCL]]--> | |
|−|* [[QA:Testcase_radeon_webgl|WebGL]] <!-- http://www.izigoo.com/izigoo/start.php --> | |
|−|* Wine - Install ' wine' and try to play your favorite game. Important: Always check if your game is supported, visit: http://appdb.winehq.org Lot of bugs are actually Wine bugs, not related to GPU drivers, so be careful | |
|−|=== Report your results === | |
|−|If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=20&component=xorg-x11-drv-ati xorg-x11-drv-ati]. If you are unsure about exactly how to file the report, just ask on IRC and we will help you. Follow the instructions on [[Xorg/Debugging|this page]] to ensure you include sufficient information in the report. Once you have completed the tests , add your results to the Results table below, following the example results from ''Example user'' as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be the model of your graphics adapter. For each test case, use the ''result'' template to enter your result, as shown in the example result line. If you could not perform one test (for example, you cannot perform the more advanced tests because the basic one fails, or you cannot perform the multihead test as you have only one display), enter the word '''N/A'''. In the comments column, you can enter the model name and PCI device ID (vendor ID is usually 1002) of your card, if you know it - you can usually find this information in the output of the command <tt>lspci -nn</tt>. | |
| || |
== Results ==
== Results ==
What to test?
Today's Fedora Test Day will focus on the radeon driver for ATI/AMD Radeon graphics cards.
If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test with your graphics card and provide feedback.
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion...
- Development -
- Quality Assurance -
What's needed to test
How to test?
Update your machine
If you're running Fedora 20, make sure you have all the current updates for it installed, using the update manager (and with the updates-testing repository enabled). Or you can use a live image:
Optionally, you may download a non-destructive Fedora 20 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.
This page provides a list of the tests to run, and lets you report your results. Clicking on a test name will show you the instructions for doing that test, and clicking 'Enter result' will let you enter your result for that test. For the Hardware name, please enter the model number for your graphics adapter as precisely as you can. You can use the
lspci -nn command to provide the PCI ID, if you are comfortable doing so.
Don't feel obliged to complete all the tests! They are listed in approximate order of importance, so if you only have time to do a few, start with the first section and work your way down. It's fine to skip any tests you can't complete, or aren't sure you understand - or you can ask in IRC for help.
If you have problems with any of the tests, report a bug to Bugzilla, usually for the component xorg-x11-drv-ati. If you are unsure about exactly how to file the report, just ask on IRC and we will help you. Follow the instructions on this page to ensure you include sufficient information in the report.
Basic tests are elementary functionality tests, expected to pass on all supported adapters. Desktop tests cover key desktop functions and again should work on all supported adapters. Video tests cover video playback: some functions may not be supported on older adapters. 3D tests cover more advanced 3D functionality; some more advanced tests may fail on hardware that is not yet fully supported. Crashes, rendering issues and glitches bugreports are more important then performance issues. Experimental tests cover more unusual and experimental functionality.