Jakub Kicinski wrote: > Hi! > > Implement support for tests which require access to a remote system / > endpoint which can generate traffic. > This series concludes the "groundwork" for upstream driver tests. > > I wanted to support the three models which came up in discussions: > - SW testing with netdevsim > - "local" testing with two ports on the same system in a loopback > - "remote" testing via SSH > so there is a tiny bit of an abstraction which wraps up how "remote" > commands are executed. Otherwise hopefully there's nothing surprising. > > I'm only adding a ping test. I had a bigger one written but I was > worried we'll get into discussing the details of the test itself > and how I chose to hack up netdevsim, instead of the test infra... > So that test will be a follow up :) > > --- > > TBH, this series is on top of the one I posted in the morning: > https://lore.kernel.org/all/20240412141436.828666-1-kuba@xxxxxxxxxx/ > but it applies cleanly, and all it needs is the ifindex definition > in netdevsim. Testing with real HW works fine even without the other > series. > > Jakub Kicinski (5): > selftests: drv-net: define endpoint structures > selftests: drv-net: add stdout to the command failed exception > selftests: drv-net: factor out parsing of the env > selftests: drv-net: construct environment for running tests which > require an endpoint > selftests: drv-net: add a trivial ping test For the series: Reviewed-by: Willem de Bruijn <willemb@xxxxxxxxxx> I left some comments for discussion, but did not spell out the more important part: series looks great to me. Thanks for building this!
