tree: fa8afe347449b4836a3cdda300ea9a38ff7a9166 [path history] [tgz]
  1. BogusFontTextTest.m
  2. golden_bogus_font_text_iPhone 8_simulator.png
  3. golden_non_full_screen_flutter_view_platform_view_iPhone 8_simulator.png
  4. golden_platform_view_clippath_iPhone 8_simulator.png
  5. golden_platform_view_cliprect_iPhone 8_simulator.png
  6. golden_platform_view_cliprrect_iPhone 8_simulator.png
  7. golden_platform_view_D211AP.png
  8. golden_platform_view_D21AP.png
  9. golden_platform_view_D321AP.png
  10. golden_platform_view_iPhone 8_simulator.png
  11. golden_platform_view_multiple_background_foreground_iPhone 8_simulator.png
  12. golden_platform_view_multiple_background_foreground_iPhone SE_simulator.png
  13. golden_platform_view_multiple_iPhone 8_simulator.png
  14. golden_platform_view_opacity_iPhone 8_simulator.png
  15. golden_platform_view_rotate_iPhone 8_simulator.png
  16. golden_platform_view_rotate_iPhone SE_simulator.png
  17. golden_platform_view_transform_iPhone 8_simulator.png
  18. golden_spawn_engine_works_iPhone 8_simulator.png
  19. GoldenImage.h
  20. GoldenImage.m
  21. GoldenPlatformViewTests.h
  22. GoldenPlatformViewTests.m
  23. GoldenTestManager.h
  24. GoldenTestManager.m
  25. Info.plist
  26. LocalizationInitializationTest.m
  27. PlatformViewGestureRecognizerTests.m
  28. PlatformViewUITests.m
  29. README.md
  30. RenderingSelectionTest.m
  31. SpawnEngineTest.h
  32. SpawnEngineTest.m
  33. StatusBarTest.h
  34. StatusBarTest.m
  35. TextSemanticsFocusTest.h
  36. TextSemanticsFocusTest.m
  37. UnobstructedPlatformViewTests.m
testing/scenario_app/ios/Scenarios/ScenariosUITests/README.md

Golden UI Tests

This folder contains golden image tests. It renders UI (for instance, a platform view) and does a screen shot comparison against a known good configuration.

The screen shots are named golden_[scenario name]_[MODEL], with _simulator appended for simulators. The model numbers for physical devices correspond to the hw.model sys call, and will represent the model numbers. Simulator names are taken from the environment.

New devices require running the test on the device, gathering the attachment from the test result and verifying it manually. Then adding an appropriately named file to this folder.

If the test is attempted on a new device, the log will contain a message indicating the file name it expected to find. The test will continue and fail, but will contain an attachment with the expected screen shot. If the screen shot looks good, add it with the correct name to the project and run the test again - it should pass this time.