From 7ee02b9f3dc1e3ef1cdc2f8f8f5dea2ad815aefb Mon Sep 17 00:00:00 2001 From: Jonathan Lee Date: Wed, 4 Dec 2024 14:18:34 -0500 Subject: [PATCH] Mention screenshot requirement --- rfcs/testdriver_in_other_types.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/rfcs/testdriver_in_other_types.md b/rfcs/testdriver_in_other_types.md index ad3f3aa..76d8fb3 100644 --- a/rfcs/testdriver_in_other_types.md +++ b/rfcs/testdriver_in_other_types.md @@ -134,8 +134,9 @@ without needing to re-parse test files themselves. As a concrete example, Gecko runs reftests using an internal endpoint, which is not set up to work with a testdriver event loop. For these vendors, an acceptable workaround might be to fall back to the - WebDriver reftest implementation, which only requires an ["execute async - script" implementation][execute-async-script]. + WebDriver reftest implementation, which only requires ["execute async + script"][execute-async-script] and ["take screenshot"][take-screenshot] + implementations. * Even with testdriver support, some APIs may still be challenging to test reliably. For example, the classic `