Not currently testing anything but I usually test Kaspersky, Norton, and some other products. I used to test WinZip before they became part of Corel.
I have and I do but only on the software I presently am using. Back in the day, I beta tested a couple of versions of PowerDesk and also Fix-It and was given copies of them for my efforts. Them was the days.
I used to. Much of that centered around SSM. Not much point in it now as I'm not going to install Vista, 7, or 8.
The only software i've beta tested properly is EAM. It's been a long time and im not as active as before there.
I voted Yes, but only because I usually install Tzuk's betas, which never seem to behave like betas, and I like having his latest software. Beyond that, however, I make it a rule to not install betas. I just appreciate the folks who do.
I used to a long time ago, but don't anymore, mostly because I have a low tolerance for bugs and problems....
Same as Page. I install SBIE betas but usually they behave like any other stable version. They are betas because changes and improvements are implemented but they always feel great after installing. Bo
Yes I beta test software. Slackware64-current, Outpost and a few others, I also alpha test. Some things are closed (signed agreements) so can't tell ya.
I beta test most of the software I use (most is freeware): debugging and testing costs, each user has a different configuration, needs, expectations, and uses the software differently. Beta testing software is useful for getting our favorite software better and a way to pay back developers.
Not beta testing anymore. Got sorta fed up with it and getting lazy. Updates on stable releases is plenty enough for me nowadays.
Occasionally for new software if its potential excites me so as to give feedback regarding general functionality to the developer. Never for upcoming releases of software I'm already using, I'm not the impatient type.
I used to beta test from now and then. Although this may not apply to the mainstream companies, I became frustrated at some of the smaller companies who would have a beta before a major upgrade. And then right when it was announced the beta was coming to an end the smaller company was acquired by a larger company. It's like the beta testing was happening to increase the final sale of the product while the takeover was going on behind the beta testers backs. I realize the beta testers are not really privy to such info as takeovers. But it is frustrating to say the least when this happens. I wish someone would do a study sometime to see how many product takeovers were announced just after a beta test for a major upgrade is finished. It seems to happen almost every time.
I don't have an extra machine to do it with, and wouldn't do it on my main box, even in a virtual environment. As such I always wait until a final build of a product to use it. And even then I wait awhile before actually using it, until a few updates and inevitable bugs are worked out. I like to see like a .1 or .2 after the version number before I jump in on it. And this is how I'm going to go about Comodo 6 too. I'll be sticking with 5.10 until I see like a 6.1 or 6.2. Same with ExploitShield, which I want to try out eventually.
I made a mistake and voted for "No, I used to beta test" It should be Never. I cannot afford to have any of my computers possibly get BSOD's because of flaky software. Admin: If possible please change my vote.
Nothing as of right now, but last week beta I tested CIS 6. I've also beta tested Vista, W-7, W-8, and Windows Server 2008 and 2012. -plus- SBIE, numerous versions of Firefox and Chrome plus any number of AV and IS applications. CTM and imaging software make it a relatively easy and risk-free experience and I find it to be (usually) fun as well as informative. (I suppose I need a REAL hobby !)