tree: 70a9573f1306711c44be650eba01a3edc8c3427e [path history] [tgz]
  1. android/
  2. benchmark/
  3. dart/
  4. fuchsia/
  5. ios/
  6. resources/
  7. rules/
  8. scenario_app/
  9. skia_gold_client/
  10. smoke_test_failure/
  11. symbols/
  12. .vpython
  13. .vpython3
  14. analysis_options.yaml
  15. analyze_core_dump.sh
  16. android_systrace_test.py
  17. assertions.h
  18. assertions_skia.cc
  19. assertions_skia.h
  20. autoreleasepool_test.h
  21. BUILD.gn
  22. canvas_test.h
  23. dart_fixture.cc
  24. dart_fixture.h
  25. dart_isolate_runner.cc
  26. dart_isolate_runner.h
  27. debugger_detection.cc
  28. debugger_detection.h
  29. display_list_testing.cc
  30. display_list_testing.h
  31. elf_loader.cc
  32. elf_loader.h
  33. fixture_test.cc
  34. fixture_test.h
  35. impeller_golden_tests_output.txt
  36. logger_listener.cc
  37. logger_listener.h
  38. lsan_suppressions.txt
  39. mock_canvas.cc
  40. mock_canvas.h
  41. mock_canvas_unittests.cc
  42. post_task_sync.cc
  43. post_task_sync.h
  44. README.md
  45. run_all_unittests.cc
  46. run_tests.py
  47. run_tests.sh
  48. sanitizer_suppressions.sh
  49. stream_capture.cc
  50. stream_capture.h
  51. test_args.cc
  52. test_args.h
  53. test_dart_native_resolver.cc
  54. test_dart_native_resolver.h
  55. test_gl_surface.cc
  56. test_gl_surface.h
  57. test_metal_context.h
  58. test_metal_context.mm
  59. test_metal_surface.cc
  60. test_metal_surface.h
  61. test_metal_surface_impl.h
  62. test_metal_surface_impl.mm
  63. test_metal_surface_unittests.cc
  64. test_timeout_listener.cc
  65. test_timeout_listener.h
  66. test_vulkan_context.cc
  67. test_vulkan_context.h
  68. test_vulkan_image.cc
  69. test_vulkan_image.h
  70. test_vulkan_surface.cc
  71. test_vulkan_surface.h
  72. testing.cc
  73. testing.gni
  74. testing.h
  75. thread_test.cc
  76. thread_test.h
  77. tsan_suppressions.txt
  78. ubsan_suppressions.txt
  79. xvfb.py
testing/README.md

Engine Testing

This directory contains the infrastructure for running tests on the engine, which are most often run by Flutter's continuous integration (CI) systems.

The tests themselves are located in other directories, closer to the source for each platform, language, and variant. For instance, macOS engine unit tests written in objective C are located in the same directory as the source files, but with a Test suffix added (e.g. “FlutterEngineTest.mm” holds the tests for “FlutterEngine.mm”, and they are located in the same directory).

Testing the Engine locally

If you are working on the engine, you will want to be able to run tests locally.

In order to learn the details of how do that, please consult the Flutter Wiki page on the subject.