Saving time with Sourcery

Some context before we begin. At eDreams ODIGEO, the iOS team is fully committed to testing and making the clean architecture of our iOS apps. We use VIPER architecture because it perfectly fits our needs. We are quite a big team, and with this architecture we are able to reach a homogeneous codebase, being able

Continue Reading

Clean architecture on Android

We all know that writing good software is tough and difficult, it’s not only about functional requirements, but also about robustness, maintainability, scalability and testability. In the android native team at eDreams ODIGEO, we researched about which architecture could be the best to solve our problems and to help us deliver quality software. Here is

Continue Reading

Selenium +Cucumber += Automated Front Tests

Who put that Selenium in my Cucumber? (Or how to test the Front-end)

Tests are key to deliver good quality to the customer, which of course is one of our main focuses. But testing this by hand usually takes too much time, time in which the customer is not benefiting from your feature. In this article we explain how we automated most of our tests of the Front-end with the help of Selenium, Cucumber and NodeJS among other technologies, which gave us the ability to speed up a lot the number of releases and time to market.

Continue Reading

Releasing TableViewKit 1.0

We are excited to release TableViewKit 1.0 – an open source framework which is a core part of our apps: eDreams, Opodo, GO Voyages (and soon Travellink). The framework allowed the eDreams ODIGEO iOS mobile team to set up a complex layout easily, while improving the modularity of our codebase. History TableViewKit was developed to

Continue Reading

Release: Decisions, Decisions

Concepts like continuous delivery, time to market or innovation are very important at eDreams ODIGEO (eDO). Working on a product like ours makes us focus on the customer. This means that we want to bring the features to them as soon as we can. The present article covers how we manage each release in the front end team and the challenges we face to take decisions around it.

Continue Reading