Zugg Software :: View topic

Posted: Wed Sep 20, 2006 1:59 am

I probably shouldn't press my luck by posting this, but I think this sets a new record for being really quiet after a release. Compared to the instant and serious bug reports from previous versions, maybe 1.06 is actually getting good enough to use.

Either that or everyone is out partying instead of mudding Very Happy

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Holy cow! If you didn't set a record on number of bug reports, you definitely set one on number of bug fixes in a single upgrade. That's gotta be easily twice that 6.26 or whatever version the big one was then.

Posted: Wed Sep 20, 2006 4:19 am

I'm pretty swamped at work so other than some light testing tonight, there's not much I'll be able to do. On the upside I leave for vacation this weekend for three weeks.

CMUD will be on the beaches of Rio de Janeiro...

And don't worry, I won't be trying very hard to test while I'm there.

Posted: Wed Sep 20, 2006 7:26 pm

Heh, I guess I spoke too soon Wink

Plenty of bug reports coming in now. Still doesn't look nearly as bad as previous versions (except for maybe the Editor bug).

I'm going to look into the Test Complete package by Automatted QA (the makers of the AQTime program I use for performance tuning, and the makers of the window docking library used in CMUD). It's a bit expensive, and it takes a lot of time to set up complete tests. But once I get tests set up, then stuff like the Editor problem shouldn't happen again.

The problem I have with CMUD right now is that there is *sooo* much stuff to test. And when I make a bug fix, it can have side effects that I can't even imagine. I usually run my test script to test the parser for obvious problems, but to catch stuff like the Editor bug, I really need to go through and test each and every screen in CMUD. And there are lots and lots of screens. Setting up some sort of automatted test system for this should help.

I haven't done this earlier because creating a test script requires that the screen you are testing is actually working. And in past versions there were so many problems that many things were not working. Now that most stuff is working (mostly) I can think about making test scripts for each screen.

Tech: Enjoy Rio! I'm jealous and we will miss you around here. Do they have WiFi on the beaches? I'm not sure if that would be a good thing or a bad thing :) But have a great vacation. Hopefully I'll have 1.07 ready when you get back.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

Posted: Wed Sep 20, 2006 8:31 pm

I actually have several *.MUD files that I use for testing. Aside from just loading them to see what happens, that's about all I can do with them. Since I don't have the time to become intimately familiar with each MUD file, I don't really know what to test once the file is loaded. I already use these files just to see if CMUD crashes when loaded, but it's very difficult to determine if there were any conversion problems since I don't know what the file is supposed to look like after it is loaded.

So for now I only ask for MUD files when I'm trying to resolve a specific problem.

Posted: Wed Sep 20, 2006 10:57 pm

Hey Zugg,

You should still have my .MUD file... which to date I have never been able to to successfully get converted. Although (1.04) did have somethings partially converted when I added.

Adept Joined: 30 Jan 2003 Posts: 228 Location: USA

I know this post has kind of gotten off topic, but to continue, thats the one problem I have found with Cmud, is I cannot to date get my file to import correct. (I know some stuff won't work due to syntax changes and the like) But the vast majority of my scripts should import from zmud to cmud properly, and it's just not happening. I know this is something you are continuously working on, but I don't think its going to get drasticly better unless you can see some of our real world examples. The easy way to see would be to open it in zmud then import it into cmud and see what works and what doesn't. Just a thought. Not Bitching, Cmud is alot better than I ever thought it would be at this point.

Posted: Thu Sep 21, 2006 4:27 pm

Davos, if you have a *.MUD file that isn't importing, then definitely send it to me. Just be sure to include some sort of details on what problems you are having, and what it is supposed to look like when it imports properly. A screenshot of what it looks like in zMUD is always useful.

Tech: I might have lost your file too if you sent it a long time ago. I know I have some files from edb, but it's hard to keep track since the names used in the email/feedback are often different than the forum handles.

But at this point, I'm not getting a lot of feedback about scripts not converting, so I think it's working for the majority of zMUD scripts. Most of the issues I have seen with conversion are covered in the "Converting zMUD scripts" article in the Support/Documentation/CMUD section of the web site.