Let’s be honest, we do not treat frontend code the same way we treat backend code. And it shows. We talk about applying rules of clean code, about keeping it simple, about writing unit tests. Yet, when it comes to writing frontend code, we skip all those rules that we usually self impose. We convinced …
This article has first appeared in Today Software Magazine. Why Spock? When we first started working on our project at work, we searched for an easy-to-use tool that would help us write readable and concise tests. We chose Spock, because in combination with Groovy it provided exactly what we needed: readable BDD-style tests that we …
The complete interview can be found on InfoQ. Adrian Bolboacă, Organizational and Technical Coach and Trainer at Mozaic Works, got interviewed by Ben Linders, InfoQ, about different types of tests, writing sufficient and good acceptance tests, criteria to decide to automate a test, and how to apply test automation to create executable specifications. Testing techniques …
Over the past 6 months, I’ve been working with a customer who develops hardware appliances. They were facing a challenge with complaints from users about one of their products, which appeared a few months in. Needless to say, the cause of such bugs requires long and thorough investigation. Context The hardware appliance runs a real-time OS, which …
Testing Strategy for a Real Time Embedded C application Read More »
This article was first published in Today Software Magazine, no 12. Below it’s the full version. The authors are: Alexandru Bolboaca and Adrian Bolboaca. The Problem Imagine the following situation: a team has developed for 6 months a great product that immediately sells. Users show their passion for the product by asking new features. If the team does not deliver the new features …
J.B. Rainsberger and Alex Bolboaca, two experienced programmers, trainers and consultants, with more than 15 years in the software development field, took the stage and answered a series of questions about how to create better software design. Their live conversation meant sharing valuable insights and new perspectives with the audience. Below you can watch the second part of the Q&A session. …
Question the software design – Part 2 – TDD and software architecture Read More »
How do we specify requirements? Chatting is inherently imprecise. Email looses context. Even the ideal requirement document starts to decay once it is done. The most precise way we know to store knowledge is code. Could we use code to write specifications that are easy to understand by non-technical stakeholders and that check the behavior …
(Guest blog post by Markus Gärtner, originally appeared on his blog. Republished with permission.) Four months have nearly past since I started my new job at it-agile GmbH. Lots of things have happened since then. I got to know many teams, I learned lots about design, architecture, test-driven development, and also about testing. This blog entry is about …
Why is it so hard to teach “what we started to call ATDD”? Read More »
(Guest blog post by Markus Gärtner, originally appeared on his blog. Republished with permission.) Last week I organized together with my colleague Meike Mertsch a Testing Dojo for a client of ours. The testers there had attended some Testing Dojos in the past, but with some drawbacks. As part of the clarification process the testers picked an internal …
by Thomas Sundberg, republished with permission Selenium a great tool for testing web applications. The current version, Selenium 2, is a merge between Selenium and WebDriver. I will walk you through an example where we test a web site using Selenium in a few different ways. This is the same example as I demonstrated …
