In response to my TestSimple 0.03 announcement, Bill N1VUX asked a number of important questions about TestSimple’s purpose. Since this is just an alpha release and I’m still making my way though the port, I haven’t created a project page or started to promote it much, yet. Once I get the harness part written and feel like it’s stable and working well, I’ll likely start to promote it as widely as possible.
So, to answer N1VUX’s questions:
Is the point to integration test the whole distributed front-ends of applications from the (EcmaScript compliant) browser?
Or to unit test the client-side java-script as an entity, mocking the server??
Yes, I would like to be able to do that eventually. I will likely mock the server by mocking XMLHttpRequest and Microsoft.XMLHTTP to return XML strings that can be used for testing. Stuff like that.
If need be, yes. The point is that you have the freedom to do it the way that makes sense to your particular project. The testing framework itself doesn’t care where it’s run or how.
Or is it more likely for driving Integration Testing from the browser with the scripting simplicity we’ve come to love, without resorting to OLE-stuffing the browser from Perl?
That was my initial impetus, yes.
Yes, as more people follow Google’s lead, more and more applications will be
ever becomes a reality (please, please, please, please please!), then we’ll
have real classes, namespaces, and even
Testing will become increasingly important as more organizations come to rely on
Looking for the comments? Try the old layout.