Hi all.. I decided to write some unit tests as an experiment and found I
got the following errors when trying to load the latest version of the SeasideTestingBundle (vR1.2-4.3,mbany dated 05/23/2005) package : Loading SeasideTestingBundle . . . (Seaside.WADispatcherEditor #test: - SCTestRunner is undeclared) (Seaside.SCSeasideForm #radioComponentForElement: - SCRadioButtonHtmlInput is undeclared) (Seaside.SCSeasideForm #getOrCreateRadioGroup: - SCRadioGroup is undeclared) (Seaside.SCSeasideForm #componentForXMLElement: - SCTextHtmlInput is undeclared) (Seaside.SCSeasideForm #componentForXMLElement: - SCCheckboxHtmlInput is undeclared) (Seaside.SCSeasideForm #componentForXMLElement: - SCHiddenHtmlInput is undeclared) (Seaside.SCSeasideForm #componentForXMLElement: - SCSubmitButtonHtmlInput is undeclared) (Seaside.SCSeasideForm #componentForXMLElement: - SCSelectHtmlInput is undeclared) (Seaside.SCSeasideForm #componentForXMLElement: - SCTextAreaHtmlInput is undeclared) Done I looked into some of the complaints above and found the first one (SCTestRunner) is defined and looks pretty much the same as the Squeak version of the code.. I've looked at a few of the others as well and they appear to have the same issue.. Could this be a namespace issue that has more to do with differences between Squeak and VW and their respective namespace handling and nothing more? I don't really see why these local classes don't seem to see each other -- and I'm sure I'm totally missing something basic here.. Any ideas? P.S. If it matters, I've got Seaside 2.6b1.30.0 dated 5/30/06 -- Rick _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
On 14 Jun 2006, at 07:40 , Rick Flower wrote: > Hi all.. I decided to write some unit tests as an experiment and > found I got the following errors when trying to load the latest > version of the SeasideTestingBundle (vR1.2-4.3,mbany dated > 05/23/2005) package : > > Loading SeasideTestingBundle . . . (Seaside.WADispatcherEditor > #test: - SCTestRunner is undeclared) (Seaside.SCSeasideForm > #radioComponentForElement: - SCRadioButtonHtmlInput is undeclared) > (Seaside.SCSeasideForm #getOrCreateRadioGroup: - SCRadioGroup is > undeclared) (Seaside.SCSeasideForm #componentForXMLElement: - > SCTextHtmlInput is undeclared) (Seaside.SCSeasideForm > #componentForXMLElement: - SCCheckboxHtmlInput is undeclared) > (Seaside.SCSeasideForm #componentForXMLElement: - SCHiddenHtmlInput > is undeclared) (Seaside.SCSeasideForm #componentForXMLElement: - > SCSubmitButtonHtmlInput is undeclared) (Seaside.SCSeasideForm > #componentForXMLElement: - SCSelectHtmlInput is undeclared) > (Seaside.SCSeasideForm #componentForXMLElement: - > SCTextAreaHtmlInput is undeclared) Done > These ugly messages can be ignored. They are all related to the load order, but in the end, VW has everything right. Since the package structure is defined in Squeak, I'm not sure if this could be fixed or not without redefining the package structure in Squeak. No, your problem will be that SeasideTesting on VW has not been updated yet for 2.6b1. The comment in the bundle says that 2.6a1.39.0 should be OK. Michel. _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Michel Bany wrote:
> These ugly messages can be ignored. They are all related to the load > order, but in the end, VW has everything right. > Since the package structure is defined in Squeak, I'm not sure if this > could be fixed or not without redefining the package structure in Squeak. > Hmm.. I'll have to keep that in mind for some recent tinkering with Magritte for VW which had tons of these sort of warnings. > No, your problem will be that SeasideTesting on VW has not been > updated yet for 2.6b1. > The comment in the bundle says that 2.6a1.39.0 should be OK. Hmm.. Is it safe to assume that the differences are more on the Seaside side of things and not necessarily due to any/many changes on the SeasideTesting side? Just curious.. -- Rick _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Rick Flower wrote:
> >> No, your problem will be that SeasideTesting on VW has not been >> updated yet for 2.6b1. >> The comment in the bundle says that 2.6a1.39.0 should be OK. > > Hmm.. Is it safe to assume that the differences are more on the > Seaside side of things and not necessarily > due to any/many changes on the SeasideTesting side? Just curious.. > I have sent various users patches to make ST work with the most recent Seaside. Unfortunately my memory is fuzzy so if you send me a walkback I'll have better luck tracking down the patch. It isn't big...one or two methods maybe. David _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
David Shaffer wrote:
> Rick Flower wrote: > > >>> No, your problem will be that SeasideTesting on VW has not been >>> updated yet for 2.6b1. >>> The comment in the bundle says that 2.6a1.39.0 should be OK. >>> >> Hmm.. Is it safe to assume that the differences are more on the >> Seaside side of things and not necessarily >> due to any/many changes on the SeasideTesting side? Just curious.. >> >> > I have sent various users patches to make ST work with the most recent > Seaside. Unfortunately my memory is fuzzy so if you send me a walkback > I'll have better luck tracking down the patch. It isn't big...one or > two methods maybe. > things out, but haven't been able to figure out how to run one once I've written it.. The tutorials for the SUnit framework I've found are specific to Squeak and not VW which is what I'm using.. Unfortunately, I've not had a chance to go dig through the VW manuals yet as I'm sure it's buried there somewhere. Anyway, once I get to some point and am stuck, I'll drop you a note.. Thanks! -- Rick _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by cdavidshaffer
David Shaffer wrote:
> I have sent various users patches to make ST work with the most recent > Seaside. Unfortunately my memory is fuzzy so if you send me a walkback > I'll have better luck tracking down the patch. It isn't big...one or > two methods maybe. > David, I've had a chance to try things out and found and fixed one of the problems : in SCComponentTestCase>>newApplicationWithRootClass: change the following line (care of an email I found from Avi I believe late last year) : addAncestor: WARenderLoopConfiguration localConfiguration. to addAncestor: WARenderLoopConfiguration new. Also, do the same to the block version of the same method (SCComponent>>newApplicationWithRootClass initializeWith) Now... Once I re-run my test, I get the following : Unhandled exception: Some XML content was expected This may be a problem with my test case.. I'll try playing around some but I'm including a shallow stack dump in case you're interested or if it jogs your memory for anything.. Thanks! -- Rick Unhandled exception: Some XML content was expected XML.DOM_SAXDriver(XML.SAXDriver)>>fatalError: Seaside.XMLDOMParser(XML.XMLParser)>>malformed: optimized [] in XML.XMLParser>>scanDocument BlockClosure>>ensure: Seaside.XMLDOMParser(XML.XMLParser)>>scanDocument Seaside.XMLDOMParser>>scanDocument Seaside.XMLDOMParser class>>parseDocumentFrom: Seaside.SCSeasideResponse>>initializeFromResponse: Seaside.SCSeasideResponse class>>fromResponse: Seaside.SCBrowserSimulator>>issueRequestUntilNotMoved: Seaside.SCBrowserSimulator>>establishSessionAtBase: Seaside.MyScripTest(Seaside.SCComponentTestCase)>>establishSession Seaside.MyScripTest>>testComponent1 Seaside.MyScripTest(TestCase)>>performTest _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |