Mailinglist Archive: yast-devel (100 mails)

< Previous Next >
Re: [yast-devel] Fail fast at Travis?
Dne 27.1.2015 v 14:28 Lukas Ocilka napsal(a):
[...]
for every single test do:
1. Redirect stderr to stdout
2. Save stdout to a temporary file
3. Check the exit code, if it passed, show: X -> passed
4. If it failed, show all the details and x -> failed
5. Remove the tempfile

Um, that would probably make sense only for the old testsuite, RSpec output can
be
used as a documentation too, see e.g. [1].

That output is useful even though there is no error, e.g. you can easily
put a link to IRC describing the behavior of a class or method...


[1] https://travis-ci.org/yast/yast-registration#L569

--

Ladislav Slez√°k
Appliance department / YaST Developer
Lihovarsk√° 1060/12
190 00 Prague 9 / Czech Republic
tel: +420 284 028 960
lslezak@xxxxxxxx
SUSE
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >