Release 1.4 has better support for more recent versions of Seaside
(tested against Seaside2.6b1-mb.84) and Squeak (first release for Squeak3.9). This version is a derivative of Release 1.3 which had a few significant API changes from the more popular 1.2. - HTML elements significantly refactored - Some selector renaming was needed (or convenient). Generally any selector which contained elements now uses entities Same for element -> entity Selector #id renamed to #cssId - Entities returned from various methods now support queries for sub-entities. So, for example, you can get back a DIV using #entityWithId: and then query that DIV for its inputs. Older releases required you to get the "form" before you could query for inputs etc. - Support for "default form action" (use #submitForm: instead of submitForm:pressingButton: or just specify nil for button) - When a component answers it is not automatically redisplayed (an intervening dialog is displayed). This is to avoid infinite loops with tasks that don't actually display anything. - Tests case entry points are now created in a sub-dispatcher ("folder"). You will want to periodically clear at this folder with: (WADispatcher default entryPoints at: 'activeTests') entryPoints copy keysAndValuesDo: [:key :value | (WADispatcher default entryPoints at: 'activeTests') removeEntryPoint: value] I haven't yet thought of a way to automate this. - A web test runner front end is included. Add an entry point with SCTestCaseMain as the root. It provides a list of test cases organized by class category. It also accepts a URL parameter named filter whose value is a wild card used to match class categories. So, for example, on my server /seaside/testRunner?filter=*SeasideTesting* shows all tests in categories matching *SeasideTesing*. This release is a derivative of one that I am using in a production system and it has proven very robust for me. Feedback is always welcomed! David _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
David Shaffer wrote:
> (WADispatcher default entryPoints at: 'activeTests') entryPoints copy > keysAndValuesDo: [:key :value | > (WADispatcher default entryPoints at: 'activeTests') > removeEntryPoint: value] > > > What do you need to automate this for? Do the tests keep on running in the background or so? I'm confused. _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Jason Johnson wrote:
> David Shaffer wrote: >> (WADispatcher default entryPoints at: 'activeTests') entryPoints copy >> keysAndValuesDo: [:key :value | >> (WADispatcher default entryPoints at: 'activeTests') >> removeEntryPoint: value] >> >> >> > > What do you need to automate this for? Do the tests keep on running > in the background or so? I'm confused. > _______________________________________________ > Seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside have >1000 test methods in my development image so after running them my image can be quite large. These entry points are never removed although their sessions do eventually expire so that memory is eventually freed. The entry points and sessions need to be retained so that you can view the test history. However, once you are done looking through the histories there is no harm in removing these. That's what this script does. I have a button on my desktop that clears seaside sessions, clears these entry points, GC's and saves my image. This makes the saves smaller and faster to load. This seems to work fine for me but I don't really think adding some type of "on save" or "on load" hook to the image makes sense. Hope that helps... David _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
I just noticed that I have a class side method is SCComponentTestCase
that clears these entry points: SCComponentTestCase clearEntryPoints David _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
I tried loading SeasideTesting 1.4 and it lists a dependency on
SAXHandler with no indication as to where to obtain it. Keith ___________________________________________________________ NEW Yahoo! Cars - sell your car and browse thousands of new and used cars online! http://uk.cars.yahoo.com/ _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Keith Hodges wrote:
> I tried loading SeasideTesting 1.4 and it lists a dependency on > SAXHandler with no indication as to where to obtain it. > > Keith > > > ___________________________________________________________ NEW Yahoo! > Cars - sell your car and browse thousands of new and used cars online! > http://uk.cars.yahoo.com/ > _______________________________________________ > Seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside believe that there is an updated one on SqueakSource but under a slightly different name). David _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by cdavidshaffer
Yes it does. Thanks for explaining it.
David Shaffer wrote: > Jason Johnson wrote: > >> David Shaffer wrote: >> >>> (WADispatcher default entryPoints at: 'activeTests') entryPoints copy >>> keysAndValuesDo: [:key :value | >>> (WADispatcher default entryPoints at: 'activeTests') >>> removeEntryPoint: value] >>> >>> >>> >>> >> What do you need to automate this for? Do the tests keep on running >> in the background or so? I'm confused. >> _______________________________________________ >> Seaside mailing list >> [hidden email] >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > SeasideTesting creates an entry point for each test method it runs. I > have >1000 test methods in my development image so after running them my > image can be quite large. These entry points are never removed although > their sessions do eventually expire so that memory is eventually freed. > The entry points and sessions need to be retained so that you can view > the test history. However, once you are done looking through the > histories there is no harm in removing these. That's what this script > does. I have a button on my desktop that clears seaside sessions, > clears these entry points, GC's and saves my image. This makes the > saves smaller and faster to load. This seems to work fine for me but I > don't really think adding some type of "on save" or "on load" hook to > the image makes sense. > > Hope that helps... > > David > > _______________________________________________ > Seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by cdavidshaffer
Keith Hodges wrote:
> Dan, I loaded in ST1.4 and poked the WACounter's 'test' link, no tests > worked and when I hit the debug button I got the following walkback. > Any ideas? > > many thanks in advance > > Keith > Keith, Darnit. This is a bug in Kom that has existed for more than a year now. I've asked Göran to fix it and even submitted a fix (attached). David 'From Squeak3.9gamma of ''23 July 2006'' [latest update: #7060] on 26 September 2006 at 7:59:37 am'! !HttpRequest methodsFor: 'initialize-release' stamp: 'cds 9/23/2006 00:59'! initRemoteAddress (stream respondsTo: #socket) ifTrue: [self remoteAddress: stream socket remoteAddress]! ! _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |