QA:Testcase Intel VT

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(create intel vt switch test case)
 
Line 12: Line 12:
 
# Switching between the graphical desktop and a virtual console should work correctly
 
# Switching between the graphical desktop and a virtual console should work correctly
 
# Both the virtual console and the graphical desktop should be displayed correctly, and this should work through repeated switches between the two
 
# Both the virtual console and the graphical desktop should be displayed correctly, and this should work through repeated switches between the two
 +
# If you are using the Test Day live CD image, you may see multiple xkb errors when switching back to the graphical desktop - this is a known issue, it does not need to be reported
 
}}
 
}}
 
[[Category:Intelvideo_Test_Cases]]
 
[[Category:Intelvideo_Test_Cases]]

Revision as of 18:25, 12 March 2009

Description

This test case tests whether virtual terminal switching works successfully with the Intel video driver, with kernel mode setting enabled. You must be using a video adapter supported by the driver, and Fedora 11 or later (or Rawhide from any time after mid-February 2009).


How to test

  1. Ensure the 'nomodeset' kernel parameter is not enabled in your bootloader configuration
  2. Ensure the file /etc/X11/xorg.conf does not exist, or is a known-good configuration file that uses the 'intel' driver
  3. Shut your system down entirely, then start it up again
  4. Switch to a virtual console: ctrl-alt-F2
  5. Log in to the console, and run a test command
  6. Switch back to the graphical desktop: ctrl-alt-F1
  7. Switch back and forth again

Expected Results

  1. Switching between the graphical desktop and a virtual console should work correctly
  2. Both the virtual console and the graphical desktop should be displayed correctly, and this should work through repeated switches between the two
  3. If you are using the Test Day live CD image, you may see multiple xkb errors when switching back to the graphical desktop - this is a known issue, it does not need to be reported