How to test PDF content Using IBM Rational Functional Tester.?

Intro

IBM® Rational® Functional Tester supports testing of Portable Document Format (PDF) read-only files created for Adobe Reader versions 7.0, 8.0, 9.0, 10.0 and 11.0. You can test PDF files that are displayed in a browser or in the stand-alone Adobe Reader application. A functional test script that is recorded for files that are displayed in the stand-alone Adobe Reader application can be played back when the file is displayed in a browser and vice-versa, provided that the script is recorded for document controls only.

Rational Functional Tester supports testing of PDF files by either interacting with specific document controls or through Reader controls.

The level of granularity that Rational Functional Tester supports depends on the way the PDF file is designed. For example, if the entire page of a PDF file is designed to contain one text object only, the verification point highlighter captures only the page-level contents and does not access the content inside the page.

Prerequisites

Before you start testing PDF files, you must set the Adobe Reader preferences and the Rational Functional Tester script assure values.

Open

Accessibility Setup Assistant.

Click Next on the Accessibility Setup Assistant page.

Select Fit page as the Default display zoom in Screen 2 of 5, and click Next.

Clear Confirm before adding tags to documents in Screen 3 of 5, and click Next.

In Screen 4 of 5:

For Page mode setting, select Deliver currently visible pages.

For Document mode setting, select Deliver the entire document at once .

Click Next.

In Screen 5 of 5, select Display PDF documents in the web browser.

Click Done.

Click Edit > Preferences in Adobe Reader.

Click the Page Display category and select Single Page as the Default Page Layout, and click OK.

For version 10.0 & 11, ensure that you disable protected mode before you set the preferences.

Supported USE Case

Typical business case for the user is to validate the content on the PDF document. The content could be a present as a link \text\table\graphic. User is interested in navigating the various pages on the pdf document, validating the content of each page or the entire document. User can also perform various options on the Adobe reader it self to achieve desired results.

Note: For RFT to interact with PDF document\Adobe reader we depend on the assisitive technology. Some times it has been observed that the way PDF document is designed ,controls are present as one complete control for eg a “Text Paragraph” would be present as one complete text control and not as each Word in the paragraph as seprate controls in which case user can do some programming in extracting the complete text and then validating the actual field he is interested in .

Frequently asked questions.

1. Which versions of pdf are supported ?
   ans) Latest RFT 8.5 supports PDF 8/9/10/11.
2. RFT hangs On PDF10 \11 ?
   ans) Did you take care of the prerequisites to disable the protected mode.
3. I need to validate a text on PDF document , but RFT captures the complete paragraph?
   ans) This might be due to the fact that the complete control is present as a seprate text control. User can make use of some programming and get the complete text use some regular expression\subtext finding algorithm to achieve the desired result.

4. Can I validate the complete page?
   Ans) Yes, user needs to perform a data verification on the complete page.

5. Can I validate the complete PDF document ?

Ans) Yes ,Only document verification points are supported in the document mode setting. A verification point can be taken after the mandatory click in the file. Any clicks on the PDF document in document mode setting while recording are ignored and no code is generated.

Use the Page mode setting for larger documents.