Share via

Office 2013 Basic Test Cases (Word)

  • Article

Basic test cases to verify that Office 2013 works with a display driver or system. Word 1. Copy Test_Word_Doc.docx to the machine where Office is installed and you are doing the testing 2. Once you've copied it, double click Test Word Doc.docx on that machine 3. Verify Word boots, the file is opened and there are no rendering issues 4. Hit Page Up and Page Down multiple times 5. Verify the pages smoothly scrolls up/down and there are no rendering issues 6. At the bottom right part of the Word window, grab, hold and move the slider bar to zoom in/out on the page 7. Verify the zooming animation is smooth and there are no rendering issues (note that as you zoom in/out the text fidelity will be low until you stop zooming where the text content will render in full fidelity) 8. Click on View in the ribbon 9. Under the Show section, check on the option for Navigation Pane 10. Verify the navigation pane smoothly animates in and there are no rendering issues In addition to specific verifications listed in the steps above, the general types of issues that may be encountered include: Application crashes Broken or missing functionality Rendering issues (ie. flickering UI, frame rate drops, piecemeal drawing, failure to repaint, choppy or slow animations) App Responsiveness problems (typing, selection, UI, "Not Responding", hangs, Inability to cancel)

Test details

   
Specifications
  • Device.Graphics.WDDM.Discretional
Platforms
  • Windows 10, client editions (x86)
  • Windows 10, client editions (x64)
  • Windows Server 2016 (x64)
Supported Releases
  • Windows 10
  • Windows 10, version 1511
  • Windows 10, version 1607
  • Windows 10, version 1703
  • Windows 10, version 1709
  • Windows 10, version 1803
  • Windows 10, version 1809
  • Windows 10, version 1903
  • Next update to Windows 10
Expected run time (in minutes) 10
Category Scenario
Timeout (in minutes) 600
Requires reboot false
Requires special configuration true
Type automatic

 

Additional documentation

Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):

More information

Parameters

Parameter name Parameter description
LLU_NetAccessOnly LLU name of net user

 

Troubleshooting

For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.