Posted by Camillo Bruni-3 on Jul 20, 2012; 4:09pm
URL: https://forum.world.st/fuelized-test-failures-tp4640954.html

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