tree: dbe51cfad8812a9c94b4cda3e2bdb2b2e2d1cebe [path history] [tgz]
  1. android_background_image/
  2. benchmark/
  3. dart/
  4. fuchsia/
  5. ios/
  6. litetest/
  7. resources/
  8. rules/
  9. scenario_app/
  10. skia_gold_client/
  11. smoke_test_failure/
  12. symbols/
  13. .vpython
  14. .vpython3
  15. analysis_options.yaml
  16. analyze_core_dump.sh
  17. android_systrace_test.py
  18. assertions.h
  19. assertions_skia.cc
  20. assertions_skia.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. lsan_suppressions.txt
  36. mock_canvas.cc
  37. mock_canvas.h
  38. mock_canvas_unittests.cc
  39. post_task_sync.cc
  40. post_task_sync.h
  41. README.md
  42. run_all_unittests.cc
  43. run_tests.py
  44. run_tests.sh
  45. sanitizer_suppressions.sh
  46. test_args.cc
  47. test_args.h
  48. test_dart_native_resolver.cc
  49. test_dart_native_resolver.h
  50. test_gl_surface.cc
  51. test_gl_surface.h
  52. test_metal_context.h
  53. test_metal_context.mm
  54. test_metal_surface.cc
  55. test_metal_surface.h
  56. test_metal_surface_impl.h
  57. test_metal_surface_impl.mm
  58. test_metal_surface_unittests.cc
  59. test_timeout_listener.cc
  60. test_timeout_listener.h
  61. test_vulkan_context.cc
  62. test_vulkan_context.h
  63. test_vulkan_image.cc
  64. test_vulkan_image.h
  65. test_vulkan_surface.cc
  66. test_vulkan_surface.h
  67. testing.cc
  68. testing.gni
  69. testing.h
  70. thread_test.cc
  71. thread_test.h
  72. tsan_suppressions.txt
  73. ubsan_suppressions.txt
  74. 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.