[squeak-dev] Continuous integration (was: All tests running green)
r.j.rothwell at gmail.com
Sat Jul 26 16:58:17 UTC 2008
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.
At which point, your report could be more...graphical?!
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
On Sat, Jul 26, 2008 at 12:30 PM, laurent laffont <laurent.laffont at gmail.com
> 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: http://www.squeaksource.com/ContIntegration.html
> To run all tests and generate a xml report per test case, type
> CITestRunner runAllTests.
> I've also made a bash script (squeakci) to run all the tests. It could
> later be run in a cron job for example:
> Here is a (basic) first report:
> It is not complete, as I have encountered some problems:
> 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
> open: aSyntaxError
> "Answer a standard system view whose model is an instance of me."
> | topView |
> <primitive: 19> "Simulation guard"
> shouldOpenDebuggerOnError ifFalse: [ ^ false ].
> Smalltalk isMorphic ifTrue:
> so before running CITestRunner, I write "SyntaxErrror openDebuggerOnError:
> false" to disable the openning of the debugger.
> I think there must be a better way to do this, but as I'm a totally
> SmallTalk newbie ... idea ?
> 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 ?
> 3. PushUpMethodTest freezes squeak
> Laurent Laffont
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev