Jaggery module testing under application (app/{appName}/module)
> One of the hard part of testing javascript modules is that when we use
> closure base privacy everything gets harder to test. Since those members
> aren’t visible other than the js scope itself we might have to think about
> our total approach to modules itself.
>
I don't think we need to address it as a part of the test framework itself.
Independent from the programming language, this kind of code smells will be
there in any code and will need a different framework such as findbugs etc.
to detect those things.
[1]
http://sidekicksrc.com/post/closures-for-classmodule-privacy-considered-harmful/
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
