Friday May 6th
This post is a request from work. As part of our ongoing effort to convert a very large application from RavenDb to Marten for its backing persistence, we want to take some time to reconsider our automated testing strategies in regards to using unit tests versus integration tests versus full end to end tests.
Editorial Note: I originally wrote this post for the NDepend blog. Go check out the original here, at their site. If you like posts about static analysis, code quality, and architecture, head on over and check it out. If you have a sadistic streak and manage a team of software developers, it's probably high entertainment ...
SpecFlow is a tool that can translate natural language scenarios (e.g. writing in English or other spoken languages) into test code. This can allow business people, users, or other stakeholders to verify that the correct features are being built. Selenium is a tool that allows test code (multiple programming languages supported) to automated a web browser.
Thursday May 5th
I don't like Lucene. It is an external dependency that works in somewhat funny ways, and the version we use is a relatively old one that has been mostly ported as-is from Java. This leads to some design decisions that are questionable (for example, using exceptions for control flow in parsing queries), or just awkward (by default, an error in merging segments will kill your entire process).