These are chat archives for Behat/Behat

9th
Sep 2016
Radosław Kłak
@rklak
Sep 09 2016 05:23
Sometimes we change code that affects many scenarios
Ciaran McNulty
@ciaranmcnulty
Sep 09 2016 07:00
You could write a formatter that outputs the errors in detail as you go, rather than at the end?
Radosław Kłak
@rklak
Sep 09 2016 07:01
exactly
Ciaran McNulty
@ciaranmcnulty
Sep 09 2016 07:01
I'm saying you could do that ;-)
Radosław Kłak
@rklak
Sep 09 2016 07:01
Its enough for me
Ciaran McNulty
@ciaranmcnulty
Sep 09 2016 07:01
I use the progress formatter to get a view of how much error there is but my suite's normally fast enough I can wait and see ;-0
Radosław Kłak
@rklak
Sep 09 2016 07:02
I just dont know that I have access to some kind of current summary during tests
Ciaran McNulty
@ciaranmcnulty
Sep 09 2016 07:02
Or you could use pretty formatter + grep somehow?
Radosław Kłak
@rklak
Sep 09 2016 07:02
Thanks, I will dive in to formatter
nice doc :D
I will handle this by my own, thanks
Ciaran McNulty
@ciaranmcnulty
Sep 09 2016 07:06
Whaaat?
docs are at behat.org - not sure what that site is
Radosław Kłak
@rklak
Sep 09 2016 07:06
oh... I just google it : D first entries