but 6.3.x was to be our first commercial version so you guys expected it to be perfect at the beginning. It is totally understandable and we anticipated it and invested allot of time in QA but as it turns out Visual WebGui is so big that we cannot QA our own framework without the open source development model. With that we will create a beta testing program which will provide committed developers that will participate in actively checking Visual WebGui.

Your posts seems to imply that you essentially have no automated testing in place and your testing is all done manually and now you are soon going to be recruiting for more testers with another new program?

I completely agree with Ryan about a unit testing program and I've brought this up before but then Gizmox never responds. You should really think about setting up a unit testing library based on WatiN or WebAii that works against the catalog or a variation of the catalog. Sometime ago, I tried to use WatiN but it wouldn't drive your forms. Maybe one of these libraries has since improved to the point that they can be used. Assuming they can, then as an alternative to people submitting small sample apps with reproducable problems they could instead submit unit test cases that run against that benchmark application and that submitted unit test case could then be added in with all the others. Outside people could also submit new forms to the benchmark application.

It would be nice to get an answer from Gizmox to ryan's, mine, and others questions regarding a StandardStudio or lite version that restores the ability to use full visual studio with the sdk.