<div dir="ltr">Nice idea...!<div><br></div><div>If you saved and categorized the errors each time you did this, you could do some long term data collection to allow developers to do some analysis around what is problematic.</div>
<div><br></div><div>At which point, your report could be more...graphical?!</div><div><br></div><div>I am currently trying to automate the output of daily Data Warehouse Integrations in a similar fashion, so I [think] I know where you are coming from...</div>
<div><br></div><div>Rob</div><div><br><div class="gmail_quote">On Sat, Jul 26, 2008 at 12:30 PM, laurent laffont <span dir="ltr"><<a href="mailto:laurent.laffont@gmail.com">laurent.laffont@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div dir="ltr">Hi,<br><br>I've started to work on a ContinuousIntegration package to periodically generate test reports for images provided by Damien Cassou (and more ?). You can find more info here: <a title="static project url" href="http://www.squeaksource.com/ContIntegration.html" target="_blank">http://www.squeaksource.com/ContIntegration.html</a><br>
To run all tests and generate a xml report per test case, type<br><br>CITestRunner runAllTests.<br><br>I've also made a bash script (squeakci) to run all the tests. It could later be run in a cron job for example: <a href="http://adhocmusic.org/squeak/squeakci" target="_blank">http://adhocmusic.org/squeak/squeakci</a> <br>
<br>Here is a (basic) first report: <br><a href="http://adhocmusic.org/squeak/squeak_test_report.html" target="_blank">http://adhocmusic.org/squeak/squeak_test_report.html</a><br><br>It is not complete, as I have encountered some problems:<br>
<br>1. some code run by the tests have syntax errors. (for example: ChildrenToSiblingsTest>>#testModelChildrenToSibling). On a syntax error squeak open the debugger and the test run stop. To run all the tests, I prefer that errors like SyntaxError generates only a test error (only for continuous integration). So I've written an ugly hacky workaround in SyntaxError>>open <br>
<br>open: aSyntaxError <br> "Answer a standard system view whose model is an instance of me."<br> | topView |<br> <primitive: 19> "Simulation guard"<br> shouldOpenDebuggerOnError ifFalse: [ ^ false ].<br>
Smalltalk isMorphic ifTrue: <br>....<br><br>so before running CITestRunner, I write "SyntaxErrror openDebuggerOnError: false" to disable the openning of the debugger. <br>I think there must be a better way to do this, but as I'm a totally SmallTalk newbie ... idea ?<br>
<br>2. Some tests require user interaction with popups, ... I want these tests to generate an error when trying to open such dialogs, as unit tests should never require user interaction. How can I do this ?<br><br><br>3. PushUpMethodTest freezes squeak<br>
<br> <br>Laurent Laffont<br><br></div>
<br><br>
<br></blockquote></div><br></div></div>