From Fedora Project Wiki

(create evince file display test)
 
(the form from pdfsamples.com is not created according to specs, use a different one)
 
(6 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{QA/Test_Case
{{QA/Test_Case
|description=This test case tests how well {{package|evince}} handles opening and displaying documents.
|description=Test opening and displaying documents using the ''Document Viewer'' (''Evince'') application.
|setup=
|setup=
# Download (or otherwise provide) some test PDF documents. Very large and complex files make good tests. [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/pdf/Installation_Guide/Red_Hat_Enterprise_Linux-6-Installation_Guide-en-US.pdf The Red Hat installation guide] is a good example, but try also to test other documents
# Make sure that ''Document Viewer'' (package {{pkg|evince}}) is installed.
# Download or copy some PDF documents to the testing environment. Very large and complex files make good tests. It's best to use your own documents, so that each tester uses different ones. But if you want some quick examples, you can use e.g. [https://opensource.adobe.com/dc-acrobat-sdk-docs/pdfstandards/PDF32000_2008.pdf PDF 1.7 specification], [https://icseindia.org/document/sample.pdf PDF with LaTex] and [https://www.irs.gov/pub/irs-pdf/fw8ben.pdf PDF form from IRS].
 
|actions=
|actions=
# Open the test document(s) with Evince (this will be the default action in the GNOME desktop if you just open the documents)
# Open the test documents with the ''Document Viewer'' app.
# Test scrolling through each document
# Test scrolling through each document.
# Test jumping to specific pages of each document, both by clicking on chapter headings in the side bar, and by entering a page number into the appropriate dialog
# Test jumping to specific pages of each document, by clicking on chapter headings in the side bar (if available), and by entering a page number in the header bar.
# Close the application
# Test jumping to specific sections by using hyperlinks in the table of contents inside the PDF (if available).
# Test zooming the document in and out, fitting to page width or the whole page.
# Test searching for a specific text inside the PDF. (Please note that national non-ascii character might often be represented differently than rendered and searching for them might not work).
# Test displaying the document in single/dual layout, in continuous/non-continuous layout, rotating pages, presenting a slideshow.
# If you have a PDF Form document (allowing to fill out forms and saving the result -- there's one such document in the samples above), fill it out with data and save the result. It's good to try to input national non-ascii characters, if you can. Then display the saved PDF, it should look as expected.
#* You can also compare ''Document Viewer'' PDF (Form) rendering with rendering the same PDF in ''Firefox''. That can help you identify potential problems.
# Perform some additional [[QA:Testcase Exploratory Testing|Exploratory testing]].
 
|results=
|results=
# The document(s) should be loaded reasonably quickly and correctly displayed
# The documents should be loaded reasonably quickly and correctly displayed.
# You should be able to scroll through the document(s) without excessive rendering delays
# All operations should behave as expected.
# You should be able to jump to specific pages in the document(s) correctly and without excessive rendering delays
# Please report all failures to the [https://gitlab.gnome.org/GNOME/evince/issues GNOME tracker].
# Evince should close correctly, and should not crash, unexpectedly close the document, or display any errors at any time during the test
}}
[[Category:Package_evince_test_cases]]
[[Category:GNOME default application test cases]]

Latest revision as of 12:26, 9 March 2023

Description

Test opening and displaying documents using the Document Viewer (Evince) application.

Setup

  1. Make sure that Document Viewer (package evince) is installed.
  2. Download or copy some PDF documents to the testing environment. Very large and complex files make good tests. It's best to use your own documents, so that each tester uses different ones. But if you want some quick examples, you can use e.g. PDF 1.7 specification, PDF with LaTex and PDF form from IRS.

How to test

  1. Open the test documents with the Document Viewer app.
  2. Test scrolling through each document.
  3. Test jumping to specific pages of each document, by clicking on chapter headings in the side bar (if available), and by entering a page number in the header bar.
  4. Test jumping to specific sections by using hyperlinks in the table of contents inside the PDF (if available).
  5. Test zooming the document in and out, fitting to page width or the whole page.
  6. Test searching for a specific text inside the PDF. (Please note that national non-ascii character might often be represented differently than rendered and searching for them might not work).
  7. Test displaying the document in single/dual layout, in continuous/non-continuous layout, rotating pages, presenting a slideshow.
  8. If you have a PDF Form document (allowing to fill out forms and saving the result -- there's one such document in the samples above), fill it out with data and save the result. It's good to try to input national non-ascii characters, if you can. Then display the saved PDF, it should look as expected.
    • You can also compare Document Viewer PDF (Form) rendering with rendering the same PDF in Firefox. That can help you identify potential problems.
  9. Perform some additional Exploratory testing.

Expected Results

  1. The documents should be loaded reasonably quickly and correctly displayed.
  2. All operations should behave as expected.
  3. Please report all failures to the GNOME tracker.
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_evince_file_display&oldid=670663"