[type_r503]

Just wondering what is the method of all you shareware gurus for testing your software? Is it better to post unfinished versions for testing or close test and post the finished copy? How do you consider your software ready for release?

-Type R 503

[kzmk]

Originally posted by type_r503:
Just wondering what is the method of all you shareware gurus for testing your software? Is it better to post unfinished versions for testing or close test and post the finished copy? How do you consider your software ready for release?

-Type R 503

we're currently creating an app, and - naturally - ran into this problem. so here's what we do/did:

first off, we decided against a public test, because the product itself is nothing new, but it has several features that are pretty unique, and we didn't want to spoil the fun or give our competitors any chance to catch up before our product even hit the shelves.
we also needed feedback on some of those features and concepts, so we started our testphase in a pre-beta stage (you couldn't save, for example), instead of implementing everything and then going beta...

so... we contacted several people we found trustworthy, told them about the product and asked if they'd like to participate in a betatest and even share thoughts on the product itself.

we then set up an online bugtracker using mantis and created accounts for round about 20 testers.

this turned out to be a smart move because we also decided to go COMPLETELY online - even for our own idea-sharing, to-do management and stuff, which we didn't keep "private", so all testers were able to comment on our ideas before we even implemented them.

so now we're in the final stages, squashing a few minor bugs and complaints, and tweaking the interface here and there. by using the bugtracker for our own thoughts, and listening to the testers, we now have at least 20 people who are pretty happy with the product we'll release.

as for the release: once the bugtracker is all "closed" bugs, we'll go public. no sooner.

just some insights. and i don't think there's a general "rule" for these things. we didn't want to go public-beta, so this sorta left us with only one option.

mantis rocks, btw...

[hayesk]

Here are my thoughts (I test hardware and software for a living, and develop software in my spare time).

Public beta-tests typically are not good methods of tracking down bugs. Most "testers" just see it as an opportunity to try out a product. Some give good feedback, most don't (if they even know how). Usually, public betas are either to appease the public when your product is late, or to get your product into customers' hands before your competitor does with a similar product.

If you don't know or can't get a private group of testers, then the public beta may be your only choice. To encourage feedback, offer free licenses to those who submit good bug reports.

Good luck.