pdfjs-dist

Tree: edd2795c17

Author	SHA1	Message	Date
Adil Allawi	5d337b1c76	Added sample OpenOffice file to tests	14 years ago
Chris Jones	e8f98f4e16	add unicode test	14 years ago
Chris Jones	2416d5e745	the new test file is a .link	14 years ago
Chris Jones	8385cb8449	the new test file is a .link	14 years ago
Chris Jones	a5e4e53cdb	the new test file is a .link	14 years ago
notmasteryet	e87ee95c79	openweb-cover test	14 years ago
notmasteryet	a7a49eabd3	openweb-cover test	14 years ago
notmasteryet	8a044058f3	Support for multi-size page PDFs	14 years ago
notmasteryet	5d154e04bf	Support for multi-size page PDFs	14 years ago
Chris Jones	29b7489a3f	add Intel ISA doc as load test, and make harness resilient to bad PDF loads	14 years ago
Chris Jones	6ca1c4cf83	add Intel ISA doc as load test, and make harness resilient to bad PDF loads	14 years ago
Rob Sayre	2793532599	Modify paths of web resources to work with test resources more buried.	14 years ago
Rob Sayre	0a8e1110a3	Modify paths of web resources to work with test resources more buried.	14 years ago
Rob Sayre	2454354b59	Move some files around.	14 years ago
Rob Sayre	0d5f92deed	Move some files around.	14 years ago
Chris Jones	375c4bf529	add support for linking pdfs we can't/won't distribute	14 years ago
Chris Jones	8bf617c844	add support for linking pdfs we can't/won't distribute	14 years ago
Chris Jones	2dff6d818c	test-harness improvements	14 years ago
Chris Jones	a64625b48d	test-harness improvements	14 years ago
Chris Jones	f7aa149778	Initial import of first test harness The harness (test.py) operates as follows. First it locates executable browsers (or symlinks or scripts) named "[browser][version]", e.g. "firefox4". It then launches the located browsers and asks them to load the file test_slave.html. At the same time, test.py sets up an HTTP server on localhost:8080 (there's a race condition here currently ;). After test_slave loads in the browser(s), it fetches the task manifest (test_manifest.json). The entries in the manifest specify which PDF to load and how many times to cycle through page rendering. This will probably evolve over time. test_slave then performs the requested tasks and POSTs the results back to test.py, which saves them. When all the results of for a task are in, test.py checks them. There are three types of tests currently. "==" tests compare the rendering of a PDF against a master copy. This is not yet implemented because setting up a master copy is complicated. "fbf" tests render all a PDF's pages, then go back to page 1 and render all pages a second time. The renderings from the first round must match the ones from the second round. "load" tests just check that a PDF's pages load without errors. Currently the test harness will only launch a "firefox4" target. This can be a bash script in your pdf.js checkout, pdf.js/firefox4, something like the following #!/bin/bash dist="/path/to/firefox4/installation" profile=`mktemp -dt 'pdf.js-test-ff-profile-XXXXXXXXXX'` $dist/firefox -no-remote -profile $profile $* rm -rf $profile (Yes, this script doesn't clean up properly on early termination.) It's possible to run the tests in a normal browsing session, but that might be annoying. With that set up, run the harness like so python test.py If all goes well, you'll see all "TEST-PASS" messages printed to stdout. If something goes wrong, you'll see "TEST-UNEXPECTED-FAIL" printed to stdout.	14 years ago
Chris Jones	7c024b89aa	Initial import of first test harness The harness (test.py) operates as follows. First it locates executable browsers (or symlinks or scripts) named "[browser][version]", e.g. "firefox4". It then launches the located browsers and asks them to load the file test_slave.html. At the same time, test.py sets up an HTTP server on localhost:8080 (there's a race condition here currently ;). After test_slave loads in the browser(s), it fetches the task manifest (test_manifest.json). The entries in the manifest specify which PDF to load and how many times to cycle through page rendering. This will probably evolve over time. test_slave then performs the requested tasks and POSTs the results back to test.py, which saves them. When all the results of for a task are in, test.py checks them. There are three types of tests currently. "==" tests compare the rendering of a PDF against a master copy. This is not yet implemented because setting up a master copy is complicated. "fbf" tests render all a PDF's pages, then go back to page 1 and render all pages a second time. The renderings from the first round must match the ones from the second round. "load" tests just check that a PDF's pages load without errors. Currently the test harness will only launch a "firefox4" target. This can be a bash script in your pdf.js checkout, pdf.js/firefox4, something like the following #!/bin/bash dist="/path/to/firefox4/installation" profile=`mktemp -dt 'pdf.js-test-ff-profile-XXXXXXXXXX'` $dist/firefox -no-remote -profile $profile $* rm -rf $profile (Yes, this script doesn't clean up properly on early termination.) It's possible to run the tests in a normal browsing session, but that might be annoying. With that set up, run the harness like so python test.py If all goes well, you'll see all "TEST-PASS" messages printed to stdout. If something goes wrong, you'll see "TEST-UNEXPECTED-FAIL" printed to stdout.	14 years ago

8 Commits (edd2795c17631028890b4a23bf9ec3b62eff4cd3)