NameSpace and Module patterns using JScript

Hi Benjamin, yes, I did further work on this, and did in fact implement a Namespace implementation using patterns similar to those used by Yahoo. This was when I was new to Test Complete and didn't have much experience with the runtime.

 

A few months later, after having had more experience with Test Complete, I removed it completely (chalk it up as a learning experience).

 

The reason why?

 

1. Script Units run in isolation, there is no real need for Namespace separation

2. Code buried in a Namespace is not available in the intellisense, this had a major impact on usability for other developers

3. Exception handling was a nightmare due to Exceptions not being propogated

4. Script Extensions provide a alternative to JScript Modules, the trick is to understand their limitations and learn to use them correctly

5. The CLR Bridge allows access to custom .Net libraries which, to be honest, kick JScript to the curb

 

I only use JScript as the glue to hold everything together, contrary to others, I use as little native JScript functionality as possible, I will always use built in or custom .Net libraries if possible and only turn to JScript features if no alternative is available.

 

The thing I have learnt is to not try and force Browser app dev patterns in Test Complete, it is it's own beast and a lot of the design patterns used in Browser dev simply do not fit.

 

Regards,

Phil Baird