Thanks Paul. I also work on the UI itself, so I know what all the Ext widgets are and how they plug together, so I just mirrored those more or less in the Java world. So I guess for this technique the tester would need to also be a developer, or at least in close collusion. Does that answer your question?
When I can find a way to abstract it out, I'd like to write another couple more quick articles extensions I've since made to the tests: 1) verification of ExtJS HTTP requests using Javascript hooks and 2) refactors I did on the Actions layer, where it now has a "fluid API" following the Builder pattern - stay tuned!
Component proxy design
Thanks Paul. I also work on the UI itself, so I know what all the Ext widgets are and how they plug together, so I just mirrored those more or less in the Java world. So I guess for this technique the tester would need to also be a developer, or at least in close collusion. Does that answer your question?
When I can find a way to abstract it out, I'd like to write another couple more quick articles extensions I've since made to the tests: 1) verification of ExtJS HTTP requests using Javascript hooks and 2) refactors I did on the Actions layer, where it now has a "fluid API" following the Builder pattern - stay tuned!