Home | History | Annotate | Download | only in tools

Lines Matching refs:Expectations

26 DEFINE_string(createExpectationsPath, "", "Path to write JSON expectations.");
29 DEFINE_string(readExpectationsPath, "", "Path to read JSON expectations from.");
112 // Files/subsets that do not have expectations. Not reported as a failure of the test so
122 // Expections read from a file specified by readExpectationsPath. The expectations must have been
232 // Stored expectations to be written to a file if createExpectationsPath is specified.
236 * If expectations are to be recorded, record the bitmap expectations into the global
237 * expectations array.
238 * As is the case with reading expectations, the key used will combine the filename
246 // Creates an Expectations object, and add it to the list to write.
247 skiagm::Expectations expectation(bitmapAndDigest);
254 * If --readExpectationsPath is set, compare this bitmap to the json expectations
262 * key will be used to find the proper expectations.
271 * - there is no expectations file.
272 * - there is an expectations file, but no expectation for this bitmap.
298 skiagm::Expectations jsExpectation = gJsonExpectations->get(name_config.c_str());
316 "expectations.",
504 // Create a string representing just the filename itself, for use in json expectations.
516 skiagm::Expectations jsExpectations = gJsonExpectations->get(name_config.c_str());
527 "new file %s (with no expectations) FAILED to decode.", srcPath);
532 // If there was a failure, and either there was no expectations file, or
533 // the expectations file listed a valid expectation, report the failure.
807 // Use an empty value for everything besides expectations, since the reader only cares
808 // about the expectations.
824 print_strings("Missing expectations", gMissingExpectations);
829 print_strings("Missing subset expectations", gMissingSubsetExpectations);