Re: [Audyssey] The beta team
Hi Philip Ok, I understand. You've got for sure many requests, and replying to all of them would take very long. So it's really the best way to post a message on the website. Regards Clauido --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/gam...@audyssey.org. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org.
Re: [Audyssey] The beta team
Hi Claudio, Well, as a game developer and someone who has run my own private beta teams I have to say there is a lot more to the selection process than you may realize. When a developer such as myself puts out a request looking for beta testers it is easy to get back several applications for the position, but only 10 to 12 out of those applications will actually be selected for the team. Therefore my job as the lead developer and beta tester is to somehow select 10 to 12 people out of 40, 50, or 60 applications for the position. The only way to do that is by looking for specific skills and qualities that would make a good beta tester in my opinion. I have to do that, because not everyone who applies for a testing position is exactly qualified for the position he/she wants. Just like any employer I pick and choose based on certain criteria which i feel would best be suited for the job. Here is a few that I personally look for. The applicant's language skills. When testing it is important for the tester to be able to clearly state his/her opinions, problem with the product, and be able to communicate effectively with the other beta testers. Since communication on a test team is vitally important I'm likely to reject an application if the applicant makes consistent grammatical and spelling errors, and the message is difficult to read. Previous experience testing software. Just like any employer I tend to look for references and prier experience testing software. It is nice for me to be able to ask developer x if he/she has had such and such an applicant as a beta tester, and how well he/she did while testing. A good reference from developer x goes a long way towards getting on my beta team, and a bad reference will put the applicant at the bottom of the list. So references are just another way for me to sort out the potential applicants. The applicant's hardware/software. Not only does a potential tester have to meet certain criteria his/her computer also may have to meet specific criteria for testing. Given the number of types of computers out there, different operating systems, processors, etc it is vitally important that a developer try and gather information on as many different computers and configurations as humanly possible during the early testing period. Now, that USA Games is now going forward with a cross-platform design initiative it will be more important than ever to include a little bit of everything in the testing process. Generally, it would be a good idea to have at least one representative for each platform targeted such as Windows XP, Windows Vista, Windows 7, Mac OS, and Linux. A team consisting of 12 users all running the same operating system would obviously be too narrow a target group, and so I may decide to reject someone on the grounds I already have the maximum number of testers for a specific target group. The applicant's reputation. As a developer I often look at the applicant's reputation or character for possible membership on one of my test teams. I wouldn't want a known software pirate for obvious reasons, and someone who is frequently disruptive on list wouldn't exactly be a good choice either. So a person's reputation will definitely be factored into my decision for beta testing. The applicant's technical skills. As a beta tester I expect an applicant to be able to perform basic computer operations such as adding and removing software from his/her computer, being able to install required dependencies on his/her own, be able to trouble shoot problems that arise during testing, and to do all of this with little to no documentation. The object of selecting a test team is to test the software, run it through various test situations, etc and the developer is not there to hold someone's hand and walk them through basic skills like installing software, removing software, deleting files, downloading software from the internet, whatever. Therefore some basic computer skills are absolutely essential for a beta tester. For example, currently I'm working on porting Mysteries of the Ancients to C++ and have already cross compiled a version for the Linux OS. Before it goes public I'll be forming a test team to test the Linux port of the game. I'd expect a tester using a Debian based Linux to be familiar with the Linux operating system as well as package add/remove tools such as dpkg and apt-get. Similarly a Red Hat based Linux user would be familiar with his/her Linux operating system as well as package add/remove tools like rpm and yum. The Linux user would have to be familiar with the Gnome desktop environment, and have basic skills using a screen reader like Orca. I'm not going to pick a Linux tester that doesn't have at least these technical skills for the position. As far as responding to each and every applicant sometimes that isn't feasible. When I announced beta testing positions for Mysteries of the Ancients I
Re: [Audyssey] The beta team
I take a lot of flack for this, but I pick people that I know well for the simple reason that i am familiar with them, and I know they'll do what I need them to. I know it's probably not fair, but it's how I like to work, and it's what works best for me. to each his own. On 1/4/10, Thomas Ward thomasward1...@gmail.com wrote: Hi Claudio, Well, as a game developer and someone who has run my own private beta teams I have to say there is a lot more to the selection process than you may realize. When a developer such as myself puts out a request looking for beta testers it is easy to get back several applications for the position, but only 10 to 12 out of those applications will actually be selected for the team. Therefore my job as the lead developer and beta tester is to somehow select 10 to 12 people out of 40, 50, or 60 applications for the position. The only way to do that is by looking for specific skills and qualities that would make a good beta tester in my opinion. I have to do that, because not everyone who applies for a testing position is exactly qualified for the position he/she wants. Just like any employer I pick and choose based on certain criteria which i feel would best be suited for the job. Here is a few that I personally look for. The applicant's language skills. When testing it is important for the tester to be able to clearly state his/her opinions, problem with the product, and be able to communicate effectively with the other beta testers. Since communication on a test team is vitally important I'm likely to reject an application if the applicant makes consistent grammatical and spelling errors, and the message is difficult to read. Previous experience testing software. Just like any employer I tend to look for references and prier experience testing software. It is nice for me to be able to ask developer x if he/she has had such and such an applicant as a beta tester, and how well he/she did while testing. A good reference from developer x goes a long way towards getting on my beta team, and a bad reference will put the applicant at the bottom of the list. So references are just another way for me to sort out the potential applicants. The applicant's hardware/software. Not only does a potential tester have to meet certain criteria his/her computer also may have to meet specific criteria for testing. Given the number of types of computers out there, different operating systems, processors, etc it is vitally important that a developer try and gather information on as many different computers and configurations as humanly possible during the early testing period. Now, that USA Games is now going forward with a cross-platform design initiative it will be more important than ever to include a little bit of everything in the testing process. Generally, it would be a good idea to have at least one representative for each platform targeted such as Windows XP, Windows Vista, Windows 7, Mac OS, and Linux. A team consisting of 12 users all running the same operating system would obviously be too narrow a target group, and so I may decide to reject someone on the grounds I already have the maximum number of testers for a specific target group. The applicant's reputation. As a developer I often look at the applicant's reputation or character for possible membership on one of my test teams. I wouldn't want a known software pirate for obvious reasons, and someone who is frequently disruptive on list wouldn't exactly be a good choice either. So a person's reputation will definitely be factored into my decision for beta testing. The applicant's technical skills. As a beta tester I expect an applicant to be able to perform basic computer operations such as adding and removing software from his/her computer, being able to install required dependencies on his/her own, be able to trouble shoot problems that arise during testing, and to do all of this with little to no documentation. The object of selecting a test team is to test the software, run it through various test situations, etc and the developer is not there to hold someone's hand and walk them through basic skills like installing software, removing software, deleting files, downloading software from the internet, whatever. Therefore some basic computer skills are absolutely essential for a beta tester. For example, currently I'm working on porting Mysteries of the Ancients to C++ and have already cross compiled a version for the Linux OS. Before it goes public I'll be forming a test team to test the Linux port of the game. I'd expect a tester using a Debian based Linux to be familiar with the Linux operating system as well as package add/remove tools such as dpkg and apt-get. Similarly a Red Hat based Linux user would be familiar with his/her Linux operating system as well as package add/remove tools like rpm and yum. The Linux user would have to be familiar with the Gnome
Re: [Audyssey] The beta team
Great insight, Tom. I hope everyone who wishes to become a beta tester for any game developer keeps your opinions in mind. I, for one, am keeping this post for future reference, and, if you give your OK, would like to pass it on to others? I would also think this a worthwhile addition to an issue of Audyssey.Thanks. --- In God we trust! - Original Message - From: Thomas Ward thomasward1...@gmail.com To: Gamers Discussion list gamers@audyssey.org Sent: Monday, January 04, 2010 11:53 AM Subject: Re: [Audyssey] The beta team Hi Claudio, Well, as a game developer and someone who has run my own private beta teams I have to say there is a lot more to the selection process than you may realize. When a developer such as myself puts out a request looking for beta testers it is easy to get back several applications for the position, but only 10 to 12 out of those applications will actually be selected for the team. Therefore my job as the lead developer and beta tester is to somehow select 10 to 12 people out of 40, 50, or 60 applications for the position. The only way to do that is by looking for specific skills and qualities that would make a good beta tester in my opinion. I have to do that, because not everyone who applies for a testing position is exactly qualified for the position he/she wants. Just like any employer I pick and choose based on certain criteria which i feel would best be suited for the job. Here is a few that I personally look for. The applicant's language skills. When testing it is important for the tester to be able to clearly state his/her opinions, problem with the product, and be able to communicate effectively with the other beta testers. Since communication on a test team is vitally important I'm likely to reject an application if the applicant makes consistent grammatical and spelling errors, and the message is difficult to read. Previous experience testing software. Just like any employer I tend to look for references and prier experience testing software. It is nice for me to be able to ask developer x if he/she has had such and such an applicant as a beta tester, and how well he/she did while testing. A good reference from developer x goes a long way towards getting on my beta team, and a bad reference will put the applicant at the bottom of the list. So references are just another way for me to sort out the potential applicants. The applicant's hardware/software. Not only does a potential tester have to meet certain criteria his/her computer also may have to meet specific criteria for testing. Given the number of types of computers out there, different operating systems, processors, etc it is vitally important that a developer try and gather information on as many different computers and configurations as humanly possible during the early testing period. Now, that USA Games is now going forward with a cross-platform design initiative it will be more important than ever to include a little bit of everything in the testing process. Generally, it would be a good idea to have at least one representative for each platform targeted such as Windows XP, Windows Vista, Windows 7, Mac OS, and Linux. A team consisting of 12 users all running the same operating system would obviously be too narrow a target group, and so I may decide to reject someone on the grounds I already have the maximum number of testers for a specific target group. The applicant's reputation. As a developer I often look at the applicant's reputation or character for possible membership on one of my test teams. I wouldn't want a known software pirate for obvious reasons, and someone who is frequently disruptive on list wouldn't exactly be a good choice either. So a person's reputation will definitely be factored into my decision for beta testing. The applicant's technical skills. As a beta tester I expect an applicant to be able to perform basic computer operations such as adding and removing software from his/her computer, being able to install required dependencies on his/her own, be able to trouble shoot problems that arise during testing, and to do all of this with little to no documentation. The object of selecting a test team is to test the software, run it through various test situations, etc and the developer is not there to hold someone's hand and walk them through basic skills like installing software, removing software, deleting files, downloading software from the internet, whatever. Therefore some basic computer skills are absolutely essential for a beta tester. For example, currently I'm working on porting Mysteries of the Ancients to C++ and have already cross compiled a version for the Linux OS. Before it goes public I'll be forming a test team to test the Linux port of the game. I'd expect a tester using a Debian based Linux to be familiar with the Linux operating system as well as package add/remove tools such as dpkg and apt-get. Similarly a Red Hat based Linux user would be familiar
[Audyssey] The beta team
Hello all One big problem I want to menzion here is, that I and my friend tryed to get into a beta-team. We couldn't enter, and we didn't receive an ansver about it. That's a problem in my eyes, because we were interested in testing it, and so I think the minimum would be to get an ansver from the developer saying that the team is already created. I don't know, but I feel that sometimes some people can come easily into the team, and others are trying and trying and couldn't do it. . So I think that nobody should be prefered. Everyone should have the possibility to enter the team. Regards Claudio --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/gam...@audyssey.org. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org.
Re: [Audyssey] The beta team
Yes, I was having the same situation. I was not among the testers, don't know why, and didn't receive the answer about the thing. Milos Przic msn: milos.pr...@gmail.com skype: Milosh-hs - Original Message - From: Claudio Zeni claudio.z...@bluewin.ch To: 'Gamers Discussion list' gamers@audyssey.org Sent: Sunday, January 03, 2010 12:13 PM Subject: [Audyssey] The beta team Hello all One big problem I want to menzion here is, that I and my friend tryed to get into a beta-team. We couldn't enter, and we didn't receive an ansver about it. That's a problem in my eyes, because we were interested in testing it, and so I think the minimum would be to get an ansver from the developer saying that the team is already created. I don't know, but I feel that sometimes some people can come easily into the team, and others are trying and trying and couldn't do it. . So I think that nobody should be prefered. Everyone should have the possibility to enter the team. Regards Claudio --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/gam...@audyssey.org. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org. __ Information from ESET NOD32 Antivirus, version of virus signature database 4738 (20100102) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus signature database 4738 (20100102) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/gam...@audyssey.org. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org.
Re: [Audyssey] The beta team
Hi Claudio and Milos. A private team usually has a limmited number of testers and I am sure every one who applied for a beta team didn't get in at some point. Sometimes the developer posts a news item on their website or on this list, but personally replying to each respondant isn't practical. Some people also want to have reasons why they are not on the team, arguing with the developer, when all that happens is that the team is full. Remember that you don't have any right to the game and the developer has no obligation to anyone, especially with a beta. - Original Message - From: Claudio Zeni claudio.z...@bluewin.ch To: 'Gamers Discussion list' gamers@audyssey.org Sent: Sunday, January 03, 2010 1:13 PM Subject: [Audyssey] The beta team Hello all One big problem I want to menzion here is, that I and my friend tryed to get into a beta-team. We couldn't enter, and we didn't receive an ansver about it. That's a problem in my eyes, because we were interested in testing it, and so I think the minimum would be to get an ansver from the developer saying that the team is already created. I don't know, but I feel that sometimes some people can come easily into the team, and others are trying and trying and couldn't do it. . So I think that nobody should be prefered. Everyone should have the possibility to enter the team. Regards Claudio --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/gam...@audyssey.org. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org. --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/gam...@audyssey.org. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org.
Re: [Audyssey] The beta team
Hi Willem, Claudio and others, This is very true. While a beta applicant may feel that his or her own application should warrent an immediate inclusion in the team, this may not always be the case and what one has to consider is, while the applicant has only their own application to worry about in this case the developer may have 40. In the case of Bgt, for example, I received many excellent applications and yet I had to accept some and reject some. I was not able to respond personally to everyone, or I would still be doing it to this day. This is not showing any disrespect on my part, as I did post a message saying that the beta application submissions were now closed and that those who were chosen would be contacted within one or two days. This, I think, is all that I could really do while still keeping things practical. Kind regards, Philip Bennefall - Original Message - From: Willem dwill...@gmail.com To: Gamers Discussion list gamers@audyssey.org Sent: Sunday, January 03, 2010 3:03 PM Subject: Re: [Audyssey] The beta team Hi Claudio and Milos. A private team usually has a limmited number of testers and I am sure every one who applied for a beta team didn't get in at some point. Sometimes the developer posts a news item on their website or on this list, but personally replying to each respondant isn't practical. Some people also want to have reasons why they are not on the team, arguing with the developer, when all that happens is that the team is full. Remember that you don't have any right to the game and the developer has no obligation to anyone, especially with a beta. - Original Message - From: Claudio Zeni claudio.z...@bluewin.ch To: 'Gamers Discussion list' gamers@audyssey.org Sent: Sunday, January 03, 2010 1:13 PM Subject: [Audyssey] The beta team Hello all One big problem I want to menzion here is, that I and my friend tryed to get into a beta-team. We couldn't enter, and we didn't receive an ansver about it. That's a problem in my eyes, because we were interested in testing it, and so I think the minimum would be to get an ansver from the developer saying that the team is already created. I don't know, but I feel that sometimes some people can come easily into the team, and others are trying and trying and couldn't do it. . So I think that nobody should be prefered. Everyone should have the possibility to enter the team. Regards Claudio --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/gam...@audyssey.org. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org. --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/gam...@audyssey.org. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org. No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.431 / Virus Database: 270.14.124/2596 - Release Date: 01/01/10 09:20:00 --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/gam...@audyssey.org. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org.
Re: [Audyssey] The beta team
well I currently don't have much in the way of an offline carrier. I have always liked to test and such and try to get into every project. These game projects are good things and I will continue to do them however these are not usually earning me cash. Yes free games are all well and good but its not earning me cash. I eventually want to try for one of the main screen reader dev test teams. since thats where most of the stuff is or some major big project or something. Maybe some support work. I'll always find time for this sort of stuff though. At 12:13 a.m. 4/01/2010, you wrote: Hello all One big problem I want to menzion here is, that I and my friend tryed to get into a beta-team. We couldn't enter, and we didn't receive an ansver about it. That's a problem in my eyes, because we were interested in testing it, and so I think the minimum would be to get an ansver from the developer saying that the team is already created. I don't know, but I feel that sometimes some people can come easily into the team, and others are trying and trying and couldn't do it. . So I think that nobody should be prefered. Everyone should have the possibility to enter the team. Regards Claudio --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/gam...@audyssey.org. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org. --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/gam...@audyssey.org. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org.
Re: [Audyssey] The beta team
oh and by the way, like everyone else I read what I want and enter it if I can. I am in the line just like everyone else. I'd have liked to get in the test team for q9 but i at first didn't want to bother and then the team filled up. You should also know that testing is not the be all, end all. there may be gaps betwene projects, or they may be stopped canciled and cued. Its like the video game project with jaffar. As far as I know its in coding so I am in the cue. What do I have to lose? Well posting my picture and some info potentually to the net. Ok no big deal in the scheme of things, its not like I have had to send my credit card number. Just know that its not as rosy as you may think, its good while it lasts but you need to wait for these sorts of things. At 12:13 a.m. 4/01/2010, you wrote: Hello all One big problem I want to menzion here is, that I and my friend tryed to get into a beta-team. We couldn't enter, and we didn't receive an ansver about it. That's a problem in my eyes, because we were interested in testing it, and so I think the minimum would be to get an ansver from the developer saying that the team is already created. I don't know, but I feel that sometimes some people can come easily into the team, and others are trying and trying and couldn't do it. . So I think that nobody should be prefered. Everyone should have the possibility to enter the team. Regards Claudio --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/gam...@audyssey.org. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org. --- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org. You can make changes or update your subscription via the web, at http://audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/gam...@audyssey.org. If you have any questions or concerns regarding the management of the list, please send E-mail to gamers-ow...@audyssey.org.
