tree: 2706c7c3ff879a8546c9acc187d6f375f6d404f6 [path history] [tgz]
  1. BUILD.gn
  2. chrome_screen_ai.proto
  3. DEPS
  4. main_content_extractor_proto_convertor.cc
  5. main_content_extractor_proto_convertor.h
  6. main_content_extractor_proto_convertor_unittest.cc
  7. README.md
  8. view_hierarchy.proto
  9. visual_annotator_proto_convertor.cc
  10. visual_annotator_proto_convertor.h
  11. visual_annotator_proto_convertor_unittest.cc
services/screen_ai/proto/README.md

Main content extraction proto convertor unittests

Creating/updating an expected proto output.

  1. Turn on WRITE_DEBUG_PROTO in main_content_extractor_proto_convertor_unittest.cc.
  2. Run its services unittests under the suite of MainContentExtractorProtoConvertorTest. An example command line is:
    out/Debug/services_unittests --gtest_filter=MainContentExtractorProtoConvertor*
    
  3. Run the following gqui command to convert a debug binary proto into an expected text proto:
    gqui from rawproto:[DEBUG PROTO PATH] proto screenai.ViewHierarchy --noprotoprint_annotations --outfile=textproto:[OUTPUT TEXTPROTO PATH]
    
  4. Delete the most outer curly brackets in the text proto.
  5. Rename the text proto based on kProtoConversionSampleExpectedFileNameFormat in main_content_extractor_proto_convertor_unittest.cc.
  6. Move the text proto to services/test/data/screen_ai.