Comments on: QotD: Beta Testing http://nslog.com/2005/09/25/qotd_beta_testing The Weblog of Erik J. Barzeski Wed, 23 May 2012 23:05:21 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Chuck Plater's Blog http://nslog.com/2005/09/25/qotd_beta_testing#comment-16965 Chuck Plater's Blog Fri, 30 Sep 2005 15:08:44 +0000 http://nslog.com/2005/09/25/qotd_beta_testing/#comment-16965 <strong>QotD: Beta Testing</strong> QotD: Beta Testing: Question: Have you ever beta tested any software (in an official capacity, not by warezing an early build of Photoshop 17 or something)? My Answer: Yes. Back in the day I was a beta tester for... QotD: Beta Testing

QotD: Beta Testing: Question: Have you ever beta tested any software (in an official capacity, not by warezing an early build of Photoshop 17 or something)? My Answer: Yes. Back in the day I was a beta tester for...

]]> By: Tim Buchheim http://nslog.com/2005/09/25/qotd_beta_testing#comment-16963 Tim Buchheim Tue, 27 Sep 2005 18:29:53 +0000 http://nslog.com/2005/09/25/qotd_beta_testing/#comment-16963 yeah, lots of stuff. Everything from the Apple IIgs version of Wolfenstein to the various PS2 online betas (mostly just server load testing, with the exception of the Everquest Online Adventures beta, which was a true beta .. I reported dozens of bugs, and Final Fantasy XI, where there were a few bugs to be found) to the last couple of Mac OS X releases (yes, legal, through an ADC Select membership). yeah, lots of stuff. Everything from the Apple IIgs version of Wolfenstein to the various PS2 online betas (mostly just server load testing, with the exception of the Everquest Online Adventures beta, which was a true beta .. I reported dozens of bugs, and Final Fantasy XI, where there were a few bugs to be found) to the last couple of Mac OS X releases (yes, legal, through an ADC Select membership).

]]> By: Moo! The Musings of a Plaid Cow http://nslog.com/2005/09/25/qotd_beta_testing#comment-16964 Moo! The Musings of a Plaid Cow Tue, 27 Sep 2005 01:15:24 +0000 http://nslog.com/2005/09/25/qotd_beta_testing/#comment-16964 <strong>QotD: Beta Testing</strong> Question: Have you ever beta tested any software (in an official capacity, not by warezing an early build of Photoshop 17 or something)? Yes, I’ve beta tested quite a few different pieces of software: Quicken for two years (Trinity and... QotD: Beta Testing

Question: Have you ever beta tested any software (in an official capacity, not by warezing an early build of Photoshop 17 or something)? Yes, I’ve beta tested quite a few different pieces of software: Quicken for two years (Trinity and...

]]> By: Bud Landry http://nslog.com/2005/09/25/qotd_beta_testing#comment-16962 Bud Landry Mon, 26 Sep 2005 03:26:14 +0000 http://nslog.com/2005/09/25/qotd_beta_testing/#comment-16962 Seems like I have been involved in quite a few large scale "public betas" (including one associated with this email address). I am not sure if that qualifies for your question. I suppose these days, "Public Beta" indeed means, "No communication or feedback expected or acknowledged". You may be reading this in a browser that is a "public beta." But occasionally, being officially corralled as a beta tester did lead to actual discussion between users and programmers (or at least PR staff), via mail list or bulletin board or other forum. Bug reports were sometimes expected, and suggestions sometimes heeded. At other times, support or beta gatherings were rogue, perhaps including a sympathetic coding insider, and filled with frustrated best intentions, Official response to bugs and UI feature tweak requests often did not consist of more than a new build and a bug fix report, which might include our finds and concerns. Frequently, it may as well have been a brick wall, and it was not unusual for response to be 'if a limb offend thee, cut it off', with an update of a particular program actually going BACKWARD in evolution. Is it still beta testing if there is no regular discussion or report of your work? Seems like I have been involved in quite a few large scale "public betas" (including one associated with this email address). I am not sure if that qualifies for your question.

I suppose these days, "Public Beta" indeed means, "No communication or feedback expected or acknowledged". You may be reading this in a browser that is a "public beta."

But occasionally, being officially corralled as a beta tester did lead to actual discussion between users and programmers (or at least PR staff), via mail list or bulletin board or other forum. Bug reports were sometimes expected, and suggestions sometimes heeded.

At other times, support or beta gatherings were rogue, perhaps including a sympathetic coding insider, and filled with frustrated best intentions, Official response to bugs and UI feature tweak requests often did not consist of more than a new build and a bug fix report, which might include our finds and concerns. Frequently, it may as well have been a brick wall, and it was not unusual for response to be 'if a limb offend thee, cut it off', with an update of a particular program actually going BACKWARD in evolution.

Is it still beta testing if there is no regular discussion or report of your work?

]]>