Parameterize runner to use custom test

[vikki]

I wondered if there were plans to build in support to run custom tests? I was considering forking the project to add my own tests (by tests I mean modules that would run instead of "scroll" or "load") but I think its fairly simple to extend the project to accept modules via the CLI so wondered if that was something you'd planned in, or for which you'd accept a PR?

I was thinking of something like either extending the "test" flag to accept a path to a module, instead of just the names of the existing ones, or else a separate flag. Either way that would then replace the testPath variable that ends up being passed into flow via the steps array - something like that? Sorry if I've missed this and it already exists BTW!

Thanks!

[paullewis]

It's something I'm planning, yes. Very much on my list is to break the runner out to its own repo, and then have you create your own test and npm install the runner, and off you go. Just give me a little time, and I'll ship it 👍

[axemclion]

Browser-perf collects similar metrics, and here is how I implemented the way to run custom actions - link