• Software developers and the Lonesome Cowboy Reflex

    In this post I’ll try to a explain a phenomenon I often notice in software development teams as one of the major causes of underperformance: the Lonesome Cowboy Reflex.  I’ll try to explain exactly what I mean and give some ideas on how it can be handled.

    July 13, 2015 by Arne Vandamme
  • Embarking on a Drupal 8 adventure

    Foreach is not a Drupal only company; we have almost 10 years of experience in Drupal, but we did our first large Drupal project (>200 mandays) only 2 years ago. Although we had some struggles in the beginning of the project, we quickly saw some benefits of building solutions with Drupal. Since this first project, we have selected Drupal 7 for several new projects and one of our teams is continuously working in Drupal/PHP.

    July 2, 2015 by Jens Steppe
  • 9 tips for improving Cucumber test readability

    This blog entry was originally posted on our Cucumber Web Bridge site.

    Even when automating UI tests, it is important to keep your scenarios as readable as possible, or you threaten to lose all benefits from a plain-text approach. In this post I’ll give you some tips that can help you with the basics.

    June 25, 2015 by Arne Vandamme
  • Code Coverage for Acceptance Tests

    Recently, I've talked about our test-setup. What I didn't mention was that we also check our code coverage to see how well our unit tests are covering the production code. This way, we can easily see how well we are testing  what we are delivering. There are plenty of tools around the block to do this. All these tools have unit tests in mind. What they do is run all the unit tests and see for each module and each and every method and even every code unit within every method if the unit tests get there.

    September 4, 2014 by Maïkel Vandorpe
  • How we go about Testing

    Nowadays, every software company has a strategy to test their code before releasing it to the customer. This can be manual testing done by someone who is less of a techy or by a co-developer or even by the developer who wrote the initial code. Manual testing can be done in many different ways, ranging from exploratory testing – just click here and there a bit – up to strictly following use cases that have been made up by a test manager. This manual testing already goes around for quite some time and is still subject to change.

    August 12, 2014 by Maïkel Vandorpe