This is the ninth post for the build phase in the first Build-Measure-Learn cycle. In the last post I described the implementation to pass the failing acceptance test. This first solution is based on the import service of the application layer, but it is missing the presentation on the user interface. In this post, I will describe the first step building a user interface, the implementation of an import dialog with file upload and a simple document view. Of course, this implementation will be guided by an acceptance test.
This is the eighth post for the build phase in the first Build-Measure-Learn cycle. In the last post I set up the first acceptance test, which has failed because the implementation is still based on mocks. In this post, I will describe the implementation with Apache Tika to enable it to pass the test. Continue reading “Apache Tika to the Rescue”
This is the seventh post in the first Build-Measure-Learn cycle.
In the last post, I introduced the Hexagonal Architecture as regulative power driving the application towards a domain centric design. In this blog post, I describe the first implementation step. It covers the implementation of an acceptance test with Cucumber guided by the Hexagonal Architecture style. I will pick up the first scenario for a puncture of the automated tests. As a result, there will be a failing acceptance test. Continue reading “Writing a Failing Acceptance Test with Cucumber”