Hi Ralph,
On 5/9/07, Ralph Johnson <[EMAIL PROTECTED]> wrote:
I've been trying to find a package in Package Universe that runs all
the tests, and it is very hard. I'm trying to make a system that
makes sure that changes to the image don't break any of the packages
already in Package Universe, but so far I can't find one where the
tests aren't already broken.
When I run the tests on squeak-dev, I get a syntax error on
ChildrenToSiblingTest
Syntax errors stop the test runner, so you can't run suites if one of
the tests has a syntax errors. After deleting that class, there were
10 failues and 30 errors in the Refactoring BrwoserTest hierarchy.
This isn't going to be much help, but it is very easy to modify SUnit to
catch syntax errors. Here's what I did:
!TestResult methodsFor: 'running' stamp: 'eem 4/3/2007 14:10'!
runCase: aTestCase
| testCasePassed |
testCasePassed := true.
[[aTestCase runCase]
on: self class failure
do:
[:signal |
failures add: aTestCase.
testCasePassed := false.
signal return: false]]
on: self class error, self class syntaxError
do:
[:signal |
errors add: aTestCase.
testCasePassed := false.
signal return: false].
testCasePassed ifTrue: [passed add: aTestCase]! !
!TestResult class methodsFor: 'exceptions' stamp: 'eem 4/3/2007 14:10'!
syntaxError
^SyntaxErrorNotification! !
HTH
Lots of tests pop up a user interface, making them impossible to run
completely automatically. You can run them if you are prepared to sit
at the machine and press buttons. Tests should be completely
automatic.
I tried to just laod SmaCC. However, it won't load. It ought to
depend on SmaCC runtime, but doesn't. Instead, it depends on a bunch
of other things, such as the refactoring browser, which has the
problems mentioned for squeak-dev.
I decided to just load RoelTyper. I could run all the tests in the
TestRunner, there was just one or two extra failures, which I thought
was pretty good, all things considering. However, when I try to run
all the tests like "TestCase suite run" then the image crashes. The
backup font for BitstreamVeraSans 9 Roman is BitstreamVeraSans 9
Roman, so TTCFont>>glyphInfoOn:into: got into an infinite loop. Why
would RoelTyper change any fonts? It seems very strange to me.
I haven't tried that many packages yet. Surely one of them will work!
-Ralph
_______________________________________________
V3dot10 mailing list
[email protected]
http://lists.squeakfoundation.org/mailman/listinfo/v3dot10
_______________________________________________
V3dot10 mailing list
[email protected]
http://lists.squeakfoundation.org/mailman/listinfo/v3dot10
