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 :) > > v2: > - rename endpoint -> remote > - use 2001:db8:: v6 prefix > - add a note about persistent SSH connections > - add the kernel config > v1: https://lore.kernel.org/all/20240412233705.1066444-1-kuba@xxxxxxxxxx > > Jakub Kicinski (6): > selftests: drv-net: add stdout to the command failed exception > selftests: drv-net: add config for netdevsim > selftests: drv-net: define endpoint structures > 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 Reviewed-by: Willem de Bruijn <willemb@xxxxxxxxxx> Thanks for humoring the naming suggestions. Exciting to have this infra.
