Enforce consistency between CI, development and test environments

What is the need / problem

In too many cases we see different results in CI (Travis) and local machines (development and test), mainly running tests.

Who does it impact

All the development team.

What is the current impact of this problem

We see this quite often and more than one developer dedicated too many hours to tackle this down.

What is the benefit in focusing on this

This would improve development speed and onboarding.

Potential solutions that will solve this problem

We spot a first take on this here.

This is tech debt, rather than customer-centric feature development.

Closing this. @sigmundpetersen @sauloperez @luisramos0 @maikel feel free to do with this what you wish.

Reopened GH issue, moved to Tech here