Shad Storhaug

@rclabo I have updated the text of the original task to make it clearer. I have also broken down the task by test project. If necessary, we can further break...

I will begin working on the `Lucene.Net.Tests.Facet` tests.

@rclabo During #411 I found 2 API issues and 4 bugs (places where the code diverged from Java or were converted incorrectly to .NET). I also timed my progress and...

I will begin working on the `Lucene.Net.Tests.Join` tests.

I will begin working on the `Lucene.Net.Tests.Queries` tests.

@rclabo That's great. However, IMO it might make sense to hold off on reviewing `Lucene.Net` tests until after we have converted the exceptions and catch blocks in #446. If you...

@rclabo - #446 has been merged, so we can resume reviewing Lucene.Net (core) tests.

Thanks for putting together this PR. We definitely need benchmarks in the master branch. However, what we ought to shoot for are benchmarks that can be run by developers, added...

> I think a lot of this comes due to being half way through automation and not completing it but we had to merge to master to get the other...

@jeme Thanks, you were correct in that the original issue was lacking some context, and I have added more information to better explain the task. The `Lucene.Net.Benchmark` project was designed...