Lucas Bremgartner

The logic to read test case directories and files did not change since LFV v1. Until now, it was never posible to run test cases from subdirectories. Therefore, I consider...

Why have you decided to put each test suite into its own directory? Do you have multiple files containing testcases in each suite? If not, you could have all the...

This issue maybe addressed with the same approach as #95. So these issues are somewhat related.

Today I asked my self how hard it would be to convert the rubydebug output back to valid json. On a first try, it looks like this would not be...

@magnusbaeck What are your thoughts about this issue? Do you intend to rebase https://github.com/logstash-plugins/logstash-codec-json_lines/pull/24 or do you think we should implement something into LFV to process the `rubydebug` output?

@magnusbaeck Today I stumbled again over this issue. We store the decision, into which Elasticsearch index a particular event should be stored in a field in the `@metadata` array. Now...

@magnusbaeck Ping me, if there is something I can help with.

@magnusbaeck Today I tested a different approach to workaround this problem and the solution is surprisingly easy. Since February 2017 (https://github.com/logstash-plugins/logstash-filter-mutate/commit/a1137c9fc4ca41069235b4f6e2f752563c39bb01#diff-091009b2789afad0d76a6df256ba6ff3) the mutate filter provides support for copying fields. So...

We then could also remove the special field `__lfv_testcase` which gets added by logstash-filter-verifier (I think this only the case if used with sockets).

Glad you like the workaround. For now, I have extended the above mentioned snippet to also remove the `__lfv` prefixed data from `__metadata`: ``` filter { mutate { copy =>...