Im very nearing the completion of quite a complex editor extension, with a fair amount of editor and runtime fucntionality. I was just trying to think of the best way to test and coax out a few or many bugs.
Since it is an asset that I wish to sell I was wondering how any of you would go about this process. Would it be best to hand it out to a few people and see how they get on, and they get a free licence, or would you suggest strict internal testing by myself, as I dont have many friends that use Unity3D.
A little info about my extension. Magic Item, is an item creation tool that manages item lists and there types that are defined by the user through UI interaction. You can import and export item databases at runtime and in editor, and can create and remove items and types at runtime too. You can link items to use assets from the resources folders or asset bundles. Basically this allows you to add new items and there types at runtime with newly imported assets. You can define a types properties be it int, float or string, and apply unique values through item creation.
(If anyone is interested past the intial topic)
Would love to hear back from the community regarding the testing phase of this.
Yea, thats what I was orignally thinking, maybe a sort of call out and the first several replys gets to test. Not sure though, would be sure good to get some advice from developers that have been through this.
I was just thinking about the number of platforms, setups, use cases, etc. My asset is a bit more generic you can use it to do lots of things. So wanted to hit a lot of those use cases.
Ahh yes, I would imagine the more complex and dynamic systems would require quite a few testers, although my system is quite flexible and has quite a few features it is still quite linear and designed for one purpose. I think I will do as your planning do and send it out to users on the unity forum, but might increase the number to about 15-20.
