Closed ErichDonGubler closed 1 month ago
@sagudev, I'm hoping to at least get confirmation that d04e532c02cf13744de69183bcce05973f752dd2 actually fulfills the premise of this PR. If you want to give me a fuller review, then great (!), but I don't expect it. 🙂
@sagudev: Ah, you'd commented on the commit, but not this PR. I'll migrate that over here, and get it resolved.
In #92, I had suggested a new representation for
TestScope
whereBrowser
andTestVisibility
were two dimensions on which other products could integrate withmoz-webgpu-cts
. However, that model is wrong; Servo only really has one set of paths and runner URLs that it cares about, currently. One can observe this with thetodo!()
s that I merged in that PR. 😅 So, I'm fixing my mistake!Throw away
TestVisibility
and makeTestScope
mirrorBrowser
variants with additional, independent structure per-browser. Concretely, makeTestScope
use either aFirefoxTestScope
or aServoTestScope
, the latter of which only has aWebGpu
variant (for now).