First JavaScript testing implementation.
authorTom Sepez <tsepez@chromium.org>
Fri, 6 Feb 2015 23:58:40 +0000 (15:58 -0800)
committerTom Sepez <tsepez@chromium.org>
Fri, 6 Feb 2015 23:58:40 +0000 (15:58 -0800)
commit72feb27fc174c2139b642eb7390fffac608f6c87
tree1423f0204b98980faa56a95d095f9f3536158e6c
parent6d407bc8ce708f28a20001dbded1f67ee2c169dd
First JavaScript testing implementation.

This is a plan for testing JS inside of pdf files under pdfium:

Communication of results will be done via app.alert(), rather than
console.println(), since the latter is not hooked up to any API
callbacks.

pdfium_test.cc is modified to be more careful about use of stdout/stderr,
so that only the app.alert() and the unsupported feature callback use
stdout.  Diffing stdout against ..._expected.txt files gives the result.

I added a /javascript directory to separate these from the embeddertest
resources.

The alert callback is backported from XFA.  This was an omission.

BUG=https://code.google.com/p/pdfium/issues/detail?id=62
R=jam@chromium.org, thestig@chromium.org

Review URL: https://codereview.chromium.org/872103003
samples/pdfium_test.cc
testing/resources/javascript/app_alert.in [new file with mode: 0644]
testing/resources/javascript/app_alert.pdf [new file with mode: 0644]
testing/resources/javascript/app_alert_expected.txt [new file with mode: 0644]