I’m looking for any best practices or general advice for testing my plugin.
I’m also thinking about how and when to have other’s test it. There are a few different options I can think of:
If my plugin was already released and I was testing a new module or update I could look for tested who’ve already purchased it like Vult did, but my plugin isn’t released yet.
I could just test it myself and then release it and provide support as people run into issues, but that seems like a poor experience for those purchasing and also doesn’t leave room for iterative feedback.
So that leaves me with finding people to test the plugin before release, sharing with them a version of the plugin without any DRM, and then hope they don’t share it out any wider.
Well, normally there are a lot of members here, who will not share any beta-releases of commercial plug-ins. I am one of those, at the moment testing delexanders new algomorph. I think this forum consists mostly of trustworthy members, so option 3 will be your best bet. Happy to help, if you need a beta test. But please provide a manual or tutorial, so we know what to test it against. Win10 here with VCV-Pro.
I offer a DRM-free pre-release build to people who want to test, and then given them a free license after release.
To my knowledge, no-one has ever leaked the pre-release build. If you were really worried about that, put a timeout on it (but as hemmer said, do make it very clear that you’ve done so).
I don’t recall anyone volunteering to test but then taking their free license without providing useful feedback. This community is a collection of the world’s finest people.
You can create a private group conversation here on the forum, by sending a Private Message to multiple people at once. That way, your testers get to bounce ideas off each other as well as communicating with you directly. Put out a public call for testers first, then when you have enough volunteers, start that private group conversation. You can add people to it later if you want.
Testing things yourself is unlikely to be enough. This is modular synthesis, where anything goes - I would never have thought to drive my sequencer with a 4,000Hz clock, but someone did, and uncovered a bug.
A word of warning: when you ask for feedback, you get it! Be ready for far more bug reports and feature requests than you thought possible. And when that happens, you owe it to the testers to keep up with them, so make sure you have the time available to do that (or if you can’t, then set the expectation that your responses might be delayed).
Being a beta tester (for the excellent @slimechildaudio ) has been one of the most rewarding experiences I’ve had here. I would never dream of sullying that experience by leaking the modules I had been entrusted to test. I don’t think I’m the exception - I firmly believe that few people here would. If you were concerned though, you could always take a look here on the forum at the folks who volunteer. You don’t have to accept everyone and based on what you can see and infer (past experience beta testing, helpful feedback to devs, pro-social behavior, etc), you could probably hand-select a good cadre for your needs.
hehe, that is my specialty, I still use your shapetracker ‘all wrong’ as you once said Though only uncover bugs now and then, did test Algomorph as well as anything else someone wants to have tested by someone who just plugs stuff in to see what happens ;). Leaking unreleased stuff is a no-no indeed, and like most here seem to feel I am not alone in that