Re: fuelized test failures
Posted by
Mariano Martinez Peck on
Jul 24, 2012; 2:29pm
URL: https://forum.world.st/fuelized-test-failures-tp4640954p4641301.html
On Fri, Jul 20, 2012 at 6:09 PM, Camillo Bruni
<[hidden email]> 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
and I get:
FLClassNotFound: Materialization error. Class named #HDTestReport not found
That happens because during serialization the graph somehow reached the class HDTestReport (probably a sender at some point in the stack). But now, when materializing, such class is not present. So...is there in the workspace an image with the jenkins stuff?
Anyway, the idea was to include this directly in Pharo, wasn't it?
Thanks
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
--
Mariano
http://marianopeck.wordpress.com