Ok wait edit what I just said. Did you just change your post to say "final testing" because I don't think it said that the first time I read it lol. I dunna what "Final Testing" means. I'm sure it's just saying it's passed the preliminary tests for an OS, it probably doesn't have any major bugs. They probably have to see how it runs on a few different phones though.
From what I understand, in VZW there are several steps to testing an OS.
The last step is "friendly user testing"
Patches - one of CB members is very close to someone who actually does the testing, I think. He can correct me if I'm wrong. And he states that .148 is finishing the last phase of testing today. As a result, we *should* hear something from him, today, tomorrow, or Monday regarding the status of this testing.
If, and I do mean IF, it passes this phase of testing, we should see VZW release it as official.
This is what I understand, and Patches can correct me if I'm wrong.
I just don't understand what's taking so long when we have brilliant minds on this board who have fixed most issues on their own...What's the testing criteria? BTW, thanks 08757...Hope you not teasing us...
every carrier has a different network and different standards, so some carriers can pass a build that has mms issues for example, but the carrier doesn't support mms on a blackberry, so none of the users will be impacted. that same build could be sent to another carrier and failed because they have mms.
and CB users can't test for network compatibility, or radiation emission, or if updating the OS adversely effects the network, other devices, causes a security flaw, or if it causes mis-provisioning on your account, etc...
so i'm unclear as to your query. did i answer all of your questions?
i'd say we're parallel to the friendly user, since all of the VZW test builds we've seen got leaked from VZW testers
and we don't HAVE to test so we don't get paid, it's a volunteer basis.
and honestly, we're only capable of about 1/5th of the testing they're responsible. a lot of the stuff we do is device testing, we can't test radio transmission, signal strength, and other implications that an OS could have beyond what we can see/experience.
and honestly, we're only capable of about 1/5th of the testing they're responsible. a lot of the stuff we do is device testing, we can't test radio transmission, signal strength, and other implications that an OS could have beyond what we can see/experience.
Wouldn't those things fall under the lab/network phase? Isn't the "friendly user" phase essentially seeing how it behaves from a user perspective, but including formal test scenarios the users are supposed to perform and provide feedback on?
As others have stated, thank you for your insight into the testing process.
Wouldn't those things fall under the lab/network phase? Isn't the "friendly user" phase essentially seeing how it behaves from a user perspective, but including formal test scenarios the users are supposed to perform and provide feedback on?
yeah kinda. but there is more to the "user perspective" part, and the formal test script they're given includes actions/tests that would require access to some network/user tools that we don't have...
Yep... I've said it before and I'll say it again. The testing script moves pretty fast.... You don't stop and take a look around once in a while, you might miss a bug or two.
I think this needs to be changed to Real World Testing. RWT. IRL would hold true for network testing as well... unless you guys think that network testing is science fiction.