|

»

CruiseControl.rb

»

CruiseControl.rb - Users

Test failures and errors

View: New views

4 Messages — Rating Filter: Alert me

	Test failures and errors by Matt Wynne :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message How does the UI decide to put output from the build into the 'test failures and errors' section? I'd like our Cucumber acceptance tests failures to be shown in here, but I'm not sure what I need to do to the formatter so they are. Matt Wynne http://blog.mattwynne.net http://www.songkick.com _______________________________________________ Cruisecontrolrb-users mailing list Cruisecontrolrb-users@... http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
	Re: Test failures and errors by Donovan Bray :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Try the HTML formatter and build an artifact On Mar 11, 2009, at 3:17 AM, Matt Wynne <matt@...> wrote: > How does the UI decide to put output from the build into the 'test > failures and errors' section? > > I'd like our Cucumber acceptance tests failures to be shown in here, > but I'm not sure what I need to do to the formatter so they are. > > Matt Wynne > http://blog.mattwynne.net > http://www.songkick.com > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users@... > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users _______________________________________________ Cruisecontrolrb-users mailing list Cruisecontrolrb-users@... http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
	Re: Test failures and errors by Matt Wynne :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Sure, that would give me a similar effect, but it's not an answer to the question I asked. Is there a better place to talk to people who work on the codebase than this list? On 12 Mar 2009, at 01:10, Donovan Bray wrote: > Try the HTML formatter and build an artifact > > On Mar 11, 2009, at 3:17 AM, Matt Wynne <matt@...> wrote: > >> How does the UI decide to put output from the build into the 'test >> failures and errors' section? >> >> I'd like our Cucumber acceptance tests failures to be shown in >> here, but I'm not sure what I need to do to the formatter so they >> are. >> >> Matt Wynne >> http://blog.mattwynne.net >> http://www.songkick.com >> >> _______________________________________________ >> Cruisecontrolrb-users mailing list >> Cruisecontrolrb-users@... >> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users@... > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users Matt Wynne http://blog.mattwynne.net http://www.songkick.com _______________________________________________ Cruisecontrolrb-users mailing list Cruisecontrolrb-users@... http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
	Re: Test failures and errors by Alexey Verkhovsky-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Thu, Mar 12, 2009 at 4:22 AM, Matt Wynne <matt@...> wrote: Sure, that would give me a similar effect, but it's not an answer to the question I asked. Is there a better place to talk to people who work on the codebase than this list? CC.rb parses stdout/stderr of the build process for patterns that look like Test::Unit and RSpec test errors/failures. To add a capability to recognize Cucumber failures, you'll need to add more patterns to that parser. This is the place for questions like this. -- Alexey Verkhovsky http://alex-verkhovsky.blogspot.com/ CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] _______________________________________________ Cruisecontrolrb-users mailing list Cruisecontrolrb-users@... http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users