Luke Petre
Luke Petre
@Bing-ok Sorry, I'm not longer working with selendroid. Maybe @marcelogomez can help?
> Do failures look decent? I'm mainly looking for if a failure message includes the inputs or at least some label. Error w/ libcst.testing.utils.data_provider ``` (libcstvenv) lpetre@lpetre-mbp LibCST % python...
> How does this play with pyre? It doesn't. The arguments to the decorator aren't typechecked against the arguments of the test method. I would argue that migrating to parameterized...
I'll re-open this when my other PRs land
My primary concern with this change is that we'll deadletter for any failure. I'd rather only deadletter things that fail repeatedly. Any thoughts on how we could do that?
Could you add the concept of retention, like in the grok exporter? https://github.com/fstab/grok_exporter/blob/master/CONFIG.md#retention