Grégoire Paris

Less noise, more PRs with working tests please @j-mywheels

Please associate your email address with your Github account, or change the email in your commits to an address already associated with it.

I'm on my phone all this week end so it won't be easy . Read .travis.yml to see how to read them, and make a deliberate mistake in the existing...

It means the existing code is covered indeed :) you might want to try throwing inside the if statements now, and check that they are covered too, and add more...

You could try generating traces with xdebug_start_trace() and compare them

Maybe if a controller fowards to itself? Not sure if what I am saying is clever or utterly stupid...

Is this a duplicate of #96 ?

@Selion05 can you please use [`git bisect`](https://git-scm.com/docs/git-bisect) between 1.8.2 and 1.9.0 to determine which exact commit is faulty?

Thanks a lot! Link for the lazy: 251bd72

@gremo please help