Add command line option to ignore certain clients when reporting batch results

[shiftyp]

For my development environment, it would be nice to be able to run a single yeti hub with many browsers connected, but be able to pass a pattern or patterns to tell the yeti client to ignore certain browser user agents when reporting results. For example, I may have one app that supports IE7, but another that doesn't and I don't want the test results from IE7 reported for the latter.

I propose an argument like --ignore-agents, with the value being a pattern (regex) used to filter agents whose results are passed to the reporter. It might be better to implement the actual ignore processing on the hub so that the tests aren't even run in the ignored agents.

I'll do the work to implement this issue myself if there is a settlement on the api and implementation specifics.

[reid]

Thanks for opening this issue.

I'd request that the browsers are opt-in instead of opt-out. Also, this should happen on the hub instead of the client.

A --list option would be useful, too.

On Dec 5, 2013, at 4:58 PM, Ryan Lynch [email protected] wrote:

For my development environment, it would be nice to be able to run a single yeti hub with many browsers connected, but be able to pass a pattern or patterns to tell the yeti client to ignore certain browser user agents when reporting results. For example, I may have one app that supports IE7, but another that doesn't and I don't want the test results from IE7 reported for the latter.

I propose an argument like --ignore-agents, with the value being a pattern (regex) used to filter agents whose results are passed to the reporter. It might be better to implement the actual ignore processing on the hub so that the tests aren't even run in the ignored agents.

I'll do the work to implement this issue myself if there is a settlement on the api and implementation specifics.

—
Reply to this email directly or view it on GitHub.