Beta Testing

[Gary Puckett]

How long is a new version in Beta Testing before it is released?
Also how many people test a new version?

Thanks
Gary

[DanEpps]

This isn't meant to be a snappy reply, but it is in beta for as long as it takes to get the kinks worked out and release it to the public.

I don't know exactly how many testers there are, but there are several. Some are machine owners and some are not. I'm sure that with the ShopBot link, some are ShopBotters as well. It is a pretty good cross-section of eCabinets users.

[Gary Puckett]

Thanks Dan,

Have you ever been involved with testing a new version?
So there is no time limit , in other words they don't say here is version? you have 2 weeks to evaluate it.

How do get involved in testing a new version

Gary

[DanEpps]

Yes Gary, I am a beta tester and no, there is no time limit for testing. Sometimes it goes very quickly and other times (for major changes) it takes somewhat longer. I have seen some releases go from beta to GA in as little as two weeks while others have taken several weeks of intensive testing and programming. In short, all issues uncovered in testing must be corrected and retested. Sometimes a fix for one issue uncovers two new issues in another area of the program.

The beta testers are invited by Thermwood. Beta testing can take up quite a bit of time as the best way to test is to duplicate everything you do in the current version with the new version. It is (obviously) an unpaid effort and many users just don't have the time to devote to testing. Those of us that do participate feel that it is a service to both Thermwood and our fellow eCabinets users that we help Thermwood to put out the most error-free software possible.

[John J. Desmond]

Dan,

I can't speak for everyone but I am glad you guys take the time to beta test. It is worth the wait to get a smooth running program. You keep up the good work. I should say thanks to all beta testers. I would hate to see the complaints if it was released without testing and working out the bugs. You do what you have to do and remember, it is appreciated.

John D.

[DanEpps]

Gee John, that wasn't meant to be a shameless plug for all the grueling hours we put into testing... I come from the computer industry (over 30 years worth) and I love testing software. As it turns out, I get to play with it earlier and learn the nuances before it hits the street. Hopefully we will do a good enough job of identifying issues before it is released and everyone else will have smooth sailing.

[Joe Dusel]

I agree with Dan, but I've only got about 25 years of software engineering experience. I like getting the beta software so that I can get ahead of the curve with learning about the new features. I do wish that us folks with programming experience could sign some kind of non-disclosure agreement to get a copy of the source code as well. It would be really nice to be able to open a debugger when we have the software crash to be able to pin-point the cause of the problem.

Joe

[Gary Puckett]

OK here goes the 64,000.00 question..................... are you testing version 6 I promise I won't tell

Gary

[John J. Desmond]

I understand it wasn't a shameless plug. I was just wanting to encourage you who do this work. Sometimes the work that goes into something is not thought about when problems surface. I just wanted to thank you guys. I wished that I had the computer experience that would allow me to do this as well. But, it isn't so. So, I rely on you guys. Anyway, I look forward to using the new version when it comes out. Work fast, LOL.

[DanEpps]

OK here goes the 64,000.00 question..................... are you testing version 6 I promise I won't tell

Gary

Can't tell you. Beta testers have to agree not to discuss test versions of the software in public forums.

I understand it wasn't a shameless plug. I was just wanting to encourage you who do this work. Sometimes the work that goes into something is not thought about when problems surface. I just wanted to thank you guys. I wished that I had the computer experience that would allow me to do this as well. But, it isn't so. So, I rely on you guys. Anyway, I look forward to using the new version when it comes out. Work fast, LOL.

I knew that...Thanks John!

I agree with Dan, but I've only got about 25 years of software engineering experience. I like getting the beta software so that I can get ahead of the curve with learning about the new features. I do wish that us folks with programming experience could sign some kind of non-disclosure agreement to get a copy of the source code as well. It would be really nice to be able to open a debugger when we have the software crash to be able to pin-point the cause of the problem.

Joe

Don't need source code if they would leave debug stubs in beta distributions. As long as the stubs are present, Visual Studio can debug with step-execution of the program.

[Neville Bastian]

Dan, In your previous life you must have worked for the government. Next you will saying loose lips sink ships.

Now if I was closer a few beers might loosen those lips.

Regards

Neville

[DanEpps]

Dan, In your previous life you must have worked for the government. Next you will saying loose lips sink ships.

Now if I was closer a few beers might loosen those lips.

Regards

Neville

Actually, you are right on track there--I was in the Navy for 10 years. While there I learned very well how to say "I can neither comfirm nor deny..."