How do you do application beta testing before release? | developer.brewmp.com How do you do application beta testing before release? | developer.brewmp.com

Developer

How do you do application beta testing before release?

Our application, running on test-enabled handsets, is nearing completion, but we would like to do an approximately 100-unit beta test before full deployment. From my reading in various places, the deployment process seems to be as follows:

1 - Testing on up to 10 test-enabled handsets
2 - NSTL testing
3 - Make available through carrier
4 - Full-scale release

This doesn't leave any room for our testing. How do we get our application onto 100 or so handsets, either before or after NSTL testing, but before we release it to the world?

I'm sure I'm not the first person to ask this, but the answer doesn't seem obvious (at least to me, even after searching the forum).

Thanks,

Larry R

either get and test 100 handsets
do it on the simulator and hope for the best
have nstl test/pretest it
hire someone else to do it who has the facilities /get a publisher (or get a better publisher)
intially you should be looking at least 15 handsets

either get and test 100 handsets
do it on the simulator and hope for the best
have nstl test/pretest it
hire someone else to do it who has the facilities /get a publisher (or get a better publisher)
intially you should be looking at least 15 handsets

>>either get and test 100 handsets
I thought Qualcomm would only test-enable 10 handsets
>>do it on the simulator and hope for the best
Not really an option - the simulator and phone(s) behave somewhat differently
>>have nstl test/pretest it
I'm not clear about what's being suggested. Are you saying we should get NSTL to do testing specific to our application, and beyond True Brew testing? This might be worthwhile, but I'm still looking for *field* testing.
>>hire someone else to do it who has the facilities /get a publisher
>>(or get a better publisher)
Is this how its "normally" done - IOW publish the application but somehow limit who it is available to (to prevent it from prematurely getting out to the world)?
Thanks,
-lr

>>either get and test 100 handsets
I thought Qualcomm would only test-enable 10 handsets
>>do it on the simulator and hope for the best
Not really an option - the simulator and phone(s) behave somewhat differently
>>have nstl test/pretest it
I'm not clear about what's being suggested. Are you saying we should get NSTL to do testing specific to our application, and beyond True Brew testing? This might be worthwhile, but I'm still looking for *field* testing.
>>hire someone else to do it who has the facilities /get a publisher
>>(or get a better publisher)
Is this how its "normally" done - IOW publish the application but somehow limit who it is available to (to prevent it from prematurely getting out to the world)?
Thanks,
-lr

>I thought Qualcomm would only test-enable 10 handsets
dunno, that might be a restriction per package, they've test enabled
100s of handsets for us
>Not really an option - the simulator and phone(s) behave somewhat differently
hence the hope for the best
>I'm not clear about what's being suggested. Are you saying we should get NSTL to do testing specific to our application, and beyond True Brew testing? This might be worthwhile, but I'm still looking for *field* testing.
nstl will do a pretest for you , theres a few outside test houses with capabilities now,they'll check the app works the way its supposed too and conform
you'll only be able to sell the application after its been tested, so if you are looking for a way of somehow getting the app to end users and testing it, you'd only be able to do that after it'd passed nstl and verizon etc had launched it

>I thought Qualcomm would only test-enable 10 handsets
dunno, that might be a restriction per package, they've test enabled
100s of handsets for us
>Not really an option - the simulator and phone(s) behave somewhat differently
hence the hope for the best
>I'm not clear about what's being suggested. Are you saying we should get NSTL to do testing specific to our application, and beyond True Brew testing? This might be worthwhile, but I'm still looking for *field* testing.
nstl will do a pretest for you , theres a few outside test houses with capabilities now,they'll check the app works the way its supposed too and conform
you'll only be able to sell the application after its been tested, so if you are looking for a way of somehow getting the app to end users and testing it, you'd only be able to do that after it'd passed nstl and verizon etc had launched it

Use NSTL to test applications before you submit them for True Brew Testing.
You don't have to worry about buying handsets also.
Visit the website below.
http://www.nstl.com/apprelay/
We have used in past.

Use NSTL to test applications before you submit them for True Brew Testing.
You don't have to worry about buying handsets also.
Visit the website below.
http://www.nstl.com/apprelay/
We have used in past.

Speaking of test houses, there's one that i found to be darn good and even guarentee's that your app will pass. it's called Axiom, check them out at http://www.axiomtesting.com
they did pretesting for my buddy, gave him suggestions and kept in touch /w my friend constantly and they got a pretty fast turn around time.

Speaking of test houses, there's one that i found to be darn good and even guarentee's that your app will pass. it's called Axiom, check them out at http://www.axiomtesting.com
they did pretesting for my buddy, gave him suggestions and kept in touch /w my friend constantly and they got a pretty fast turn around time.

My impression of the 10 handset limit was that new developers are restricted to generating test signatures for 10 ESNs. But that is something that can be waived. They just don't want anyone with a Verisign cert cranking out hundreds of test sigs for all their friends...or something like that.
If you have a bone fide need for them, you can get the limits lifted.
As for beta tests...nope. Not possible outside of the testing houses of the type mentioned earlier.

My impression of the 10 handset limit was that new developers are restricted to generating test signatures for 10 ESNs. But that is something that can be waived. They just don't want anyone with a Verisign cert cranking out hundreds of test sigs for all their friends...or something like that.
If you have a bone fide need for them, you can get the limits lifted.
As for beta tests...nope. Not possible outside of the testing houses of the type mentioned earlier.