You know I was thinking along the same lines, though not really reward based since i didn't put that much thought into it, but after the slew of bugs after the world publish, how do we increase the frequency of testing and reporting on test center?I think we need an incentive to use test center. Maybe points for every hour you play there that can be turned in for stuff on a production shard. Sure it would be abused by some I'm sure, but maybe they might actually try some stuff while they're stuck there. Just a thought.
This is always a problem, people exploit an issue until someone catches it because it takes them months to fix it when they do find out.So many bugs that don't seem related to what they were actually working on. Can't imagine why that is. Wasn't this suppose to be a bug FIX patch? lol It's gotta be a nightmare to bug test. Plus a lot of bugs people find they are probably keeping it quiet till it goes liveI'm thinking they are about at the point of having created more bugs than they fixed
![]()
That idea is interesting. They could learn the game at their own pace and not limited to 14 days. As long as they fully realize it's a test center that could be wiped at any time. There have been free trials I've tried before and the trial was over before I even really played it much.Makes test center a free to play shard. New players still get 14 day trial but once that has finished its pay up or stay on test center.
Have a PROPER feedback forum. Like they had for the time of legends focus group. This way people can post about bugs and problems and the devs can moderate and reply. Keep it just to testing only (to start with).
That's an interesting picture. Do you know where it's from?everyone get behind the bug and push
![]()
Not sure I'm on board with this lol But you might be moving in the right direction. I still use the newb title Explorer of Darkness cause I think it sounds cool. How about for each person that reports a new unreported bug gets a little golden bug statue? But then the art perspective would be wrongnew player titles
Capt Lucky... lil bugger ( for those that report 10 bugs)
Capt Lucky real Bugger ( for those who report 50 bugs)
Capt Lucky Knight of Buggery![]()
Cause that's working so wellIncentive? You mean like catching bugs before the publish goes live? That should be incentive enough...they put it on Test first...then 2 other shards....plenty of time to test and find things that need to be fixed/adjusted yes?
They give us the time, it's up to us to get on there and test it.
You would think so, but how many people actually went and tested this?Incentive? You mean like catching bugs before the publish goes live? That should be incentive enough...they put it on Test first...then 2 other shards....plenty of time to test and find things that need to be fixed/adjusted yes?
They give us the time, it's up to us to get on there and test it.
I always wondered if it'd be better to have Atlantic or Great Lakes pre test publishes first.My suggestion is leave pubs on Origin longer given Origins extreme low population maybe toss in some incentive to get more people doing their day to day things there. My second suggestion is to extend deadlines on publishing when there are known bugs crawling around. More games get released with serious bugs because "We ran out of time" and then the first 1-3 months is one hot fix and patch after another.
Don't complain about it? Really? It's not my job to test their code. Send me a check and I'll think about it. NO ONE would assume the paying players have any obligation to do anything. They get my 40 bucks+ every month, I'VE DONE MY PART. To be honest I doubt any incentive would get me on test center. But it would entice some, maybe enough.And who's fault is that? That's on us...they give us the resources....so if you're not gonna use them, don't complain when bugs slip through...my 2 cents anyway![]()
EXACTLY! We are the customers and it is our part to hand over our money for a product. They are the business it is their job to deliver a quality product.Don't complain about it? Really? It's not my job to test their code. Send me a check and I'll think about it. NO ONE would assume the paying players have any obligation to do anything. They get my 40 bucks+ every month, I'VE DONE MY PART. To be honest I doubt any incentive would get me on test center. But it would entice some, maybe enough.
It's not up to us..... We do not work for EA. There does need to be a reason for people to bother with testing otherwise this is what you getIncentive? You mean like catching bugs before the publish goes live? That should be incentive enough...they put it on Test first...then 2 other shards....plenty of time to test and find things that need to be fixed/adjusted yes?
They give us the time, it's up to us to get on there and test it.
That's not on us, dude. QA is not the responsibility of the players. Obviously it's great if players help, but it's not our job, nor is it our "fault" when a publish is buggy.And who's fault is that? That's on us...they give us the resources....so if you're not gonna use them, don't complain when bugs slip through...my 2 cents anyway![]()
I think we need an incentive to use test center. Maybe points for every hour you play there that can be turned in for stuff on a production shard. Sure it would be abused by some I'm sure, but maybe they might actually try some stuff while they're stuck there. Just a thought.
my thoughts exactly. there is no way 1 qa tester can catch everything. an incentive program to report bugs encountered on test center prior to a publish sounds like a step in the right direction. those who disagree with the idea don't have to participate.You know I was thinking along the same lines, though not really reward based since i didn't put that much thought into it, but after the slew of bugs after the world publish, how do we increase the frequency of testing and reporting on test center?
Clearly they rely on us to do it for them and frankly they should just fire the QA guy, and hire another programmer.
Thanks for testing it out.A few of my quildmates and I did do the quests on TC1 and reported feedback directly to Kyronix who had stopped by while we were testing. We were able to take the quest items and lock them down and did not have any issues with the quest rewards. We were able to remove the Tiger Cub statuette and lock it down. So those bugs came about after the original tests were made. The publish had been on Origin for a week prior to going live and I don't recall seeing any reports of the lock down bug, but they made another patch just before going live so perhaps it was in that code. We only tested the quests as we didn't create copies of everything in our houses to bring over when we made the copy to test. Who would think to bring a 16th Anniversary Horse, or a Prox Swampy still in statue form? I did copy over all 4 of the Vet Crafting Tools and checked to see if they fixed the issue with the Sewing Machine requiring wood intead of leather.
Um most times I agree with you... but I have yet to receive a check for testing their products. I don't mind but when fault is placed I'd at least prefer to be originally compensated.And who's fault is that? That's on us...they give us the resources....so if you're not gonna use them, don't complain when bugs slip through...my 2 cents anyway![]()
Performers dance and carry a replica of dung beetle during opening ceremony of 2010 World Cup at Soccer City stadium in Johannesburg (south Africa)That's an interesting picture. Do you know where it's from?
I try to test what I can.1. Why should we pay to test?
2. Any idea how many many many times people do test, report, and they still send it out as it was??
3. 1+2 = no testing for me
Thanks, that was gonna "bug me" lolPerformers dance and carry a replica of dung beetle during opening ceremony of 2010 World Cup at Soccer City stadium in Johannesburg (south Africa)
Some interesting insight, thanks for sharing.I know from experience that all the testing in the world in a closed test environment doesn't begin to cover the things users do once a program gets out in the wild. We release a major version of our software about yearly. We have a couple of QA people who have multiple automated test systems on various operating systems and machine configurations. Our Support group tests it in advance of release to make sure we don't find anything and are aware of new functionality. We generally feel really solid on our releases. Sure enough, as soon as we let it out the door, a customer finds a show stopping, billing level issue that brings the world to a halt.
I'm not saying that reported bugs haven't gone unfixed and get released anyway. But I am saying that with any software that is beyond version 1, two things tend to happen. #1 You fix one thing that impacts and breaks four more. #2 The minute you let a customer touch it you are going to stand back and go "huh, they pushed what button how? why on earth would they do that?"
And just to let you know, I've worked in my current company for 16 years and done software support for 23 years. It's happened with every single software release I've ever been part of. There's a reason Microsoft puts out updates. LOL No matter how much testing is done, internally, on TC and on Origin, until this gets onto a bigger shard or more people pound away, bugs are gonna get released. Just the nature of software.The really important thing is how quickly the showstoppers get fixed. Not that they got released.
This person knows whats up.I know from experience that all the testing in the world in a closed test environment doesn't begin to cover the things users do once a program gets out in the wild. We release a major version of our software about yearly. We have a couple of QA people who have multiple automated test systems on various operating systems and machine configurations. Our Support group tests it in advance of release to make sure we don't find anything and are aware of new functionality. We generally feel really solid on our releases. Sure enough, as soon as we let it out the door, a customer finds a show stopping, billing level issue that brings the world to a halt.
I'm not saying that reported bugs haven't gone unfixed and get released anyway. But I am saying that with any software that is beyond version 1, two things tend to happen. #1 You fix one thing that impacts and breaks four more. #2 The minute you let a customer touch it you are going to stand back and go "huh, they pushed what button how? why on earth would they do that?"
And just to let you know, I've worked in my current company for 16 years and done software support for 23 years. It's happened with every single software release I've ever been part of. There's a reason Microsoft puts out updates. LOL No matter how much testing is done, internally, on TC and on Origin, until this gets onto a bigger shard or more people pound away, bugs are gonna get released. Just the nature of software.The really important thing is how quickly the showstoppers get fixed. Not that they got released.
You do know that people from other shards are MORE then welcome to come to Origin and test things there too. I was able to take the initial Valley of One Quest, did the rescue the tiger cub part, which was fun and I had no issues, but time constrains and real life leave me little time to do much else.The whole point of origin is exactly for people on production to catch bugs before it happens. If Origin's population is too small for this task, or its players are not doing their duty to report bugs then maybe the task of live test server should be moved to a shard with a bigger population.