ba-st / boardwalk Goto Github PK

The JS related tests are not running because are failing during the load:

*** Warning: Warning: This package depends on the following classes:
  JSObjectTest
You must resolve these dependencies before you will be able to load these definitions: 
  BoardwalkJavascriptTest
  BoardwalkJavascriptTest>>#testJSDeclareGlobalNamespace
  BoardwalkJavascriptTest>>#testJSObjectAsImmediatelyInvokedFunctionExpression
  BoardwalkJavascriptTest>>#testJSObjectEqualTo
  BoardwalkJavascriptTest>>#testJSObjectIdenticalTo
  BoardwalkJavascriptTest>>#testJSObjectIf
  BoardwalkJavascriptTest>>#testJSObjectIfThenElse
  BoardwalkJavascriptTest>>#testJSObjectSessionStorage
  JSFunctionCallTest
  JSFunctionCallTest>>#testCallJsFunction
  JSFunctionCallTest>>#testJavascriptContentOn
  JSFunctionCallTest>>#testJavascriptContentOnWithOneParameters
  JSFunctionCallTest>>#testJavascriptContentOnWithParameters
  JSNamedFunctionTest
  JSNamedFunctionTest>>#testJavascriptContentOn
  JSNamedFunctionTest>>#testJavascriptContentOnWithBody

WARenderingTest in Boardwalk is incompatible with WARenderingTest in Seaside 3.3.1. Rename WARenderingTest in Boardwalk (breaking backward compatibility) or extent the Seaside version.

At least + should be added to JSObject, maybe other operators as well.

To improve Willow according to ba-st/Willow#143 some changes are required in the identifier assigner.

Improvements to make the tests compatible with other projects that require more standardized protocols

Instance creation methods in hierarchies may need access to the session, but Seaside only offers it on the instance side.
This can be solved by implementing

WAObject class>>#session
^ WACurrentRequestContext value session

as an extension method in the Boardwalk package.

If you have static file contents, it's common to deploy them to a CDN or file server.
To do this, some metadata is necessary (media type or default cache duration), a tool for helping deployment of libraries and their metadata would be useful.

Things that should be included:

• full file path: library-vX.Y.Z/resource.js.
• mediatype for that resource.
• cache duration (if defined) for that resource.

Ideally this should be in a single file, so when uploading, the only thing to do is read that file and upload the resources described inside.

Add support protocol for testing ajax callbacks

To prevent page redraws from getting the same id for more than one component.

Add an extension message to WillowApplication in a Development package to set the debugger error handler:

 | application |
 application := MyWillowApplication registerAsDevelopmentApplication.
 application filter configuration
  	  at: #exceptionHandler
  	  put: WADebugErrorHandler.

To a more declarative one, like application beDebuggable or application setDebuggerErrorHandler.