
No-Try: True Bug: None Change-Id: I4ff887649145bc6c240873685f944b470c309747 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/296442 Reviewed-by: Jeremy Leconte <jleconte@google.com> Auto-Submit: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Harald Alvestrand <hta@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/main@{#39492}
1.7 KiB
Add a new test binary
This page lists all the steps needed in order to add an rtc_test
target to
WebRTC's BUILD.gn files and ensure the test binary will run on the presubmit and
postsubmit infrastructure.
-
While working on your CL, add an
rtc_test
target, withtestonly = true
, and../test:test_main
among its dependencies (rtc_test
targets require amain()
function). -
Add the newly created
rtc_test
target to thegroup("default")
target in the root BUILD.gn. The target needs to be added within thertc_include_tests
section. -
Add the name of the newly created
rtc_test
into infra/specs/gn_isolate_map.pyl. -
Add the name of the newly created
rtc_test
into infra/specs/test_suites.pyl. By default, you should add it to theandroid_tests
,desktop_tests
andios_simulator_tests
sections. -
Run the script infra/specs/generate_buildbot_json.py (no arguments) to generate the JSON scripts based on the previsouly modified .pyl scripts.
-
Build, test, review and submit!
The bots will execute the new configs as part of the CQ. Inspect some logs to verify that your test is in fact executed by the bots where you expect them to be.
The details of the (many) config files are described in https://chromium.googlesource.com/chromium/src/testing/+/HEAD/buildbot/README.md.