ostia.be
To Test Or Not To Test - Ostia
http://www.ostia.be/blog/2012/08/29/totestornottotest
To Test or Not to Test. I recently decided to participate in a RAD race. Which will be held on 9 and 10 November. A RAD race is a competition in which teams (of two people in this case) build a real-life application in two days, using the language and tools of their choice. On the technology side everything is clear. We’ll be building the app using PlayFramework. But right in the middle of the excitement Matti and I felt when we decided to enter the competition, a question popped up: what about testing.
ostia.be
Extreme Programming Explained, without explaining - Ostia
http://www.ostia.be/blog/2012/09/10/xp-explained-without-explaining
Extreme Programming Explained, Without Explaining. I’ve been reading ‘Extreme Programming Explained – Embrace Change’, by Kent Beck ( @kentbeck. If you’ve read it too, you’re probably thinking: “it’s an old book, you should’ve read it years ago”, and I agree. But if you didn’t I can only say: you should. And what better way is there to inspire than by listing up some favorite quotes. XP is an opportunity […] to realize that maybe you’ve been fine all along and just hanging with the wrong crowd. Team prog...
ostia.be
Legacy code, an epyphany - Ostia
http://www.ostia.be/blog/2013/01/29/legacy-code
Legacy Code, an Epyphany. Until recently, I used the term. For bad, ancient code that had been written ten consultants ago, for code that has stopped evolving because it’s too complicated and critical that nobody dares to take responsibility, for code that came from someone else, you get the idea. We’ve all seen that code and we all love to hate that consultant, don’t we. And then I learned about another definition of legacy code, one that Michael Feathers ( @mfeathers. Legacy code is code without tests.
ostia.be
Dojo - Ostia
http://www.ostia.be/blog/2012/10/04/dojo
The Belgian Playframework User Group held it’s first coding event last Wednesday: a Coding Dojo. The ingrediënts: 17 nice people, a decent sized room, food and drinks, and Playframework of course. Is an event where people gather to code and learn together. The goal of a dojo is exactly that: to code and learn, nothing more. It’s about the journey, not the destination. Scores them and shows an overview of all quizzers and their scores on a simple overview page. Not the destination :). That was a game chan...
ostia.be
Play 1 vs Play 2: Hold Your Horses - Ostia
http://www.ostia.be/blog/2013/02/27/play-1-vs-play-2-hold-your-horses
Play 1 vs Play 2: Hold Your Horses. I work for Cegeka, a company that’s proud of not being the regular type of body-shopping consulting firm. Instead, they put together teams of highly skilled, agile-minded people and sell those to clients as a whole. Needless to say I like it there. Self-improvement is an important part in their philosophy, and in order to do that Cegeka encourages people to participate in so-called. These are groups of people of the same profession – Spotify would call them. When we he...
ostia.be
PlayBe Dojo: Play 2 & Java - Ostia
http://www.ostia.be/blog/2012/09/18/playbe-first-dojo
PlayBe Dojo: Play 2 and Java. Last year at Devoxx, I met Steve Chaloner ( @steve objectify. A Welsh expat in Belgium, and the first guy I met who had been using PlayFramework. Professionally. Steve and his teammate managed to rewrite a struts 1 app that had been in development for some 4 years and that was ready for the bin. They used PlayFramework and rewrote the app in about a tenth of the original LOCs. Steve is also the author of Deadbolt, a widely used authorization module for both Play 1 and 2.
ostia.be
about - Ostia
http://www.ostia.be/about
Hi, I’m Ben Verbeken, an agile software developer living in Tienen (Belgium, Europe). I spend most of my professional time writing web apps in Java using the usual spring and hibernate stack. In my spare time, I prefer being a PlayFramework. Addict, only the best thing since sliced bread. Together with Steve Chaloner. I’m a co-founder of the Belgian Playframework User Group. The freedom of being a freelancer. Brahms, Mendelssohn, Schubert. My objects to be statically typed. Things I dislike, hate even.
ostia.be
play 2 JUnit runner - Ostia
http://www.ostia.be/blog/2012/10/22/play-2-test-runner
Play 2 JUnit Runner. I like Play 2. It’s simply the best thing that happened on the JVM since, well, Play 1 :). One thing bothers me though: testing is still a bit of a PITA (at least in Java). Sure, Play 2 has webdriver support, you don’t have to extend. Anymore and you can unit-test templates. But, instead of extending base test classes I have to call a bunch of static utility methods on the. In his excellent blog post. Matthieu Guillermin ( @mguillermin. Then, you can use this runner in an.
ostia.be
Using the builder pattern for test fixtures - Ostia
http://www.ostia.be/blog/2013/06/06/using-the-builder-pattern-for-test-fixtures
Using the Builder Pattern for Test Fixtures. If you read some of my previous blog posts, you may have noticed I’m quite keen on TDD. Writing good tests and writing them first is the only way I know to:. Prove your code works the way. Ensure a bug you fix now will never find its way back into production. Properly document your code without the inherent duplication of code comments. Build a good safety net for refactoring. In theory, test methods should be concise, and they should have a given-when-then.
ostia.be
First! - Ostia
http://www.ostia.be/blog/2012/08/28/first
First blog post, yay! Now with that out of the way, go ahead and read the second post. That’ll be a more interesting, I promise. Posted by Ben Verbeken. To Test Or Not To Test ». Using the builder pattern for test fixtures. Play 1 vs Play 2: Hold Your Horses. Legacy code, an epyphany. Play 2 JUnit runner.