At the QA team we have been playing for a while with Selenium Grid, a great tool to run Selenium tests in parallel.

The first task was to reduce the execution time of the Smoke Test Suite having more than one browser running the tests. This is a complex suite with a lot of dependencies, so there's a limit on the parallelization that is possible to achieve. Pablo Luján prepared a graph to explain this a little better:

Even though we have reduced the execution time of 114 tests from 160 minutes to 90 minutes. And we are working on some options to reduce this even more.

Now that the integration of our testing code has been thoroughly tested we are ready to promote the changes from the experimental branch to the stable one. But this change will require some adjustments on the jobs and scripts.

We have new components: a Selenium Hub and one or more Grid Remote Controllers. The Remote Controllers register themselves with the Hub and wait for requests. The Hub will send tests to idle RCs or queue them if none is available. And the RCs will execute the actions on his browser.

I don't know how to use doors. Not even the ones with instructions written on them. If they say "push" I pull, and if they say "pull" I push. I've been locked in, locked out and locked between doors. I can't easily find the handle to get out of my own car. Let's better not talk about keys and locks...

I'm not being particularly smart here, but it seems that the error is more common than I thought. And it seems that my stupidity is not the only cause.

"Somehow, when a device as simple as a door has to come with an instruction manual — even a one-word manual — then it is a failure, poorly designed."

Hello dear Internet. My name is Leo Arias and this is my first post for the Openbravo Planet.

I work with the QA team helping the rest of developers to build high-quality software.

I spend most of the time maintaining the repository for automated testing. Pablo Lujan, also part of the QA team, recently presented a webinar with more details of the things we have done; you can find the recorded session here.

Recently we have been polishing the automation process in order to make it easier to code new integration tests for the ERP. This post will briefly explain the last changes in the packages hierarchy and the convention we are using to name tests. If you are interested in the automation of your Openbravo installations or the modules you develop this might be useful.

El próximo sábado nos vemos en la Universidad Latina en San Pedro para celebrar la libertad.

Música gratis o música libre

«El software libre es una cuestión de libertad, no de precio. Para entender el concepto, debería pensar en libre como en libre expresión, no como en barra libre.» [1].

Así empieza el texto de definición de software libre, pero yo creo que es aplicable para todo. Lo que queremos no es que todas las cosas nos salgan gratis, pues como productores de cosas todos sabemos que si no tenemos dinero para comer no podemos producir más cosas.
Lo que queremos es tener acceso a la cultura. Yo en particular lo que quiero es que cuando recibo alguna cosa, el autor me de la posibilidad de usarla para lo que quiera, de estudiarla y modificarla, de distribuirla sin pedir permisos adicionales ni sufrir trabas legales, y de distribuir mis modificaciones también para que pueda seguir fluyendo la creatividad, ya sea que hablemos de software, música, imagen, video, mapas, o la cosa que sea.