Forums | Chat | News | Contact Us | Register | PSU Social |
PSU: Where BFR's mean Big Freaking Robots
Forums | Chat | News | Contact Us | Register | PSU Social |
Home | Forum | Chat | Wiki | Social | AGN | PS2 Stats |
|
|
Thread Tools | Search this Thread | Display Modes |
2011-07-24, 01:37 AM | [Ignore Me] #1 | ||
First Sergeant
|
I know beta testing could be a while away, but I figured Id post some key points on what/what not to do during a beta test for when it hits.
Points to keep in mind if you are chosen: 1. DO report bugs with vast amounts of information, screenshots and timestamps. 2. DO test as many features as possible in as many ways as possible. 3. DO consult with other tester's for answer's to potential problems you maybe experiencing in-game before making an angry post in the forums. 4.DO suggest as many changes with as many justifications for your creative suggestion's. ( this is a big one, it's one thing to complain about a feature or lack of then just saying "this sucks" and not give a creative explanation or remedy for the problem) 5.DO support creative new approaches to in-game abilities,play styles and progression types. The DO NOT's of beta testing: 1. DO NOT play the beta like a shareware demo - It's a beta, not a opportunity for F2P free ride. 2. DO NOT come to the forums to complain at dev's and players because the servers maybe down, usually a reason for it. 3. DO NOT expect conformity within feature sets and game play. As in comparing one game to PS2, this is a different game. 4. DO NOT play the beta for 1 day, then come and make final judgement's on "how utterly terribad this game is" because your experience was not what you expected (this is pretty common). Be realistic. 5. DO NOT talk about the game outside of beta test forums allotted to you. IE. do not tell your friends family anything about the game as it can get you in trouble under the NDA. If any one here does not know what an NDA is, it stands for Non Disclosure Agreement, its a waiver that you must sign confirming that everything during the beta test much be hush hush. If you are selected for beta, I hope you test it for the right reasons, the more feedback SOE receives during the beta the better this game will be. Best of luck! |
||
|
2011-07-24, 01:44 AM | [Ignore Me] #3 | ||
Major
|
Is there even a beta coming soon? Anyway kind of pointless to post as people will play it like its the real game anyway. That's why more MMO's are waiting until really late to do a open beta anymore. Sometimes only doing it on weekends to save costs. An pretty much treating like a demo/marketing tool.
Most of the testing will be done by professionals an small selected groups of outfits I imagine during closed beta. |
||
|
2011-07-24, 01:48 AM | [Ignore Me] #4 | |||
Lieutenant General
|
Smed has said current subscribers will be among the first into beta. suck it |
|||
|
2011-07-24, 01:52 AM | [Ignore Me] #5 | |||
First Sergeant
|
|
|||
|
2011-07-24, 02:36 AM | [Ignore Me] #8 | |||
External alpha and cb testing is usually basic functionality testing. You don't have enough bodies for any kind of stress test but you have plenty of eyes to examine interaction between systems as they are introduced. A whole lot of macro balancing happens as well.
Systems and content feedback is probably the best things an external tester can provide. Try to break things but you likely won't find much. Engines are so compartmentalized anymore that most issues are easy to track and nail down. Be objective; trying to get the game to suit your play style doesn't help anyone. Be verbose; the more relevant info you can provide on a bug or design defect, the better. Be polite; you are a guest in someone else's house.
__________________
And that was that. Last edited by exLupo; 2011-07-24 at 02:38 AM. |
||||
|
2011-07-24, 02:40 AM | [Ignore Me] #9 | |||
First Sergeant
|
|
|||
|
2011-07-24, 02:46 AM | [Ignore Me] #10 | |||
Staff Sergeant
|
If you are talking about unit testing, then yes, it can be used to ensure that the code is correct before being checked in. But where I work, bugs are still identified by manual and automated scripts, and ad-hoc testing. I can't imagine any Test Team Leaders in our place trusting only unit tests to find bugs. But then, we do have 20 year old spaghetti code with a mish-mash of UI, business and data layers. |
|||
|
2011-07-24, 02:59 AM | [Ignore Me] #11 | ||
Colonel
|
If what we've lead to believe is correct, the early beta testers may have a great deal of influence over what we end up receiving as the finished product, so I certainly hope anyone lucky enough to gets in doesn't just treat it as a try before they buy...
I'm looking at you. |
||
|
2011-07-24, 03:11 AM | [Ignore Me] #12 | ||||
The external alpha percentage is usually fairly good because they're hand picked. CB is pretty poor because it's usually machine selection. However, that's taken into account when making those numbers. You get a percentage of actual analysts and then the rest are there to provide game context for those analysts to do their jobs. Can't test in a vacuum.
__________________
And that was that. Last edited by exLupo; 2011-07-24 at 03:13 AM. |
|||||
|
2011-07-24, 05:17 AM | [Ignore Me] #15 | |||
Major
|
I'll believe it when I see it. Did he say ALL subscribers would be the first into beta? Cause if not then I could still be right. That they will pick certain outfits an do most of the testing with them. I do see your point about it being hard to test large scale combat without thousands to actually slug it out. But that doesn't mean they will open the floodgates for a year or more of testing to every subscriber. Well if you had to stay subscribed then maybe since it would pretty much be a pay to play Beta then. |
|||
|
|
Bookmarks |
|
|