Zugg Software :: View topic

Posted: Tue Jun 15, 2010 5:41 pm

The current Beta testers are doing a great job at reporting bugs with the new stringlist and table code. However, as we have seen, there are a *lot* of problems and some of them are rather obscure. There are just so many different ways to use string lists and tables in CMUD that it's hard to test everything. So we need MORE TESTERS!

I am very worried that these low-level improvements have severely impacted the stability of CMUD close to a potential public release. I really need more testers, especially people who will just sit down with CMUD and try all sorts of weird stuff to try and break it.

I'm talking about trying to break the stringlist and table code right now, not stuff like the mapper or any old obscure bugs that only effect a small number of people. What I need is real stress-testing of the stringlist and database code.

The last thing the CMUD 3.x Public Version needs is more problems with stability. The purpose of the new list and table code was to *improve* stability and performance by allowing proper support for nested lists and tables.

So if you have some time to really try to stress-test the Beta version, or if you have some friends who might be able to help, it would be much appreciated. Especially people who know how to make good bug reports and who are good at breaking stuff.

As an incentive, when CMUD 3.x Public Version is released, I'm going to pick a handful of the best beta testers and give out some free upgrades for the new version. This will be completely subjective and will be based on *quality* of bug reports and not just quantity. So here is your chance to potentially save a few bucks and also help all of the other CMUD users in the community and ensure that the 3.x public release is a great new *stable* version.

IMPORTANT NOTE: Anybody choosing to do this beta testing needs to be fully aware that I'm planning almost DAILY updates until these issues are resolved, so it will be very important to keep up with the latest updates. In fact, I plan another update later today.

Feel free to wait until after today's update to start the stress testing since there are still some pretty obvious problems.