Combine corpus runner into test_runner.py

samples/pdfium_test.cc

Index: samples/pdfium_test.cc
diff --git a/samples/pdfium_test.cc b/samples/pdfium_test.cc
index 47c8d5fe3f2c8f5d2a62f66c55ceb889f25ea9c4..a917b5e31bfd6074f2b225274558ba0a017d5705 100644
--- a/samples/pdfium_test.cc
+++ b/samples/pdfium_test.cc
@@ -816,7 +816,14 @@ int main(int argc, const char* argv[]) {
         GetFileContents(filename.c_str(), &file_length);
     if (!file_contents)
       continue;
-    fprintf(stderr, "Rendering PDF file %s.\n", filename.c_str());
+
+    std::string test_dir = "pdfium/testing/";

[Tom Sepez, 2016/05/05 16:39:08]

Feels like this shouldn't have any knowledge of the directory tree, instead
maybe give it a command line argument about where to write its result files (if
not in same directory as input files), then pass that in from the .py scripts.

[dsinclair, 2016/05/05 16:45:08]

This is just for the fprintf below. I was trying to change it so that instead of
a 200 character long path we get a 50 character path. Makes reading the output a
lot simpler. But, I only really want to do that when we're running our tests,
not for other files. So, it isn't the output dir, it's the input dir that I care
about.

+    size_t pdfium_testing = filename.find(test_dir);
+    std::string log_name = filename;
+    if (pdfium_testing != std::string::npos)
+      log_name = filename.substr(pdfium_testing + test_dir.length());
+    fprintf(stderr, "Rendering PDF file %s.\n", log_name.c_str());
+
     std::string events;
     if (options.send_events) {
       std::string event_filename = filename;