On Fri, Jul 20, 2012 at 6:09 PM, Camillo Bruni <camillobr...@gmail.com>wrote:
> From now on all the test-failures are serialized on the build server. > > This allows us to quickly find the cause of a failing test: > - download the .fuel file for the failing test > - materialize the .fuel in the image and debug the code > | aContext | > aContext := FLMaterializer materializeFromFileNamed: > 'PharoDebug.fuel'. > Debugger openContext: aContext label: 'This is the new debugger!' > contents: nil > > The serialized stack trace is very limited (generally only 2 contexts) but > they > are enough to get a decent view on what the variables are > I was thinking....it should be really easy to build a very simple UI that: - lets you select/write a Jenkins job and a test - downloads the .fuel - materialize it and open the debugger Anyone interested? Ben do you need another tool for your paper/chapter? ;) Cheers, -- Mariano http://marianopeck.wordpress.com
