Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

I am trying to submit an app today, and I keep getting a NSTL server error,
"There is a communication problem with the server. Please try to submit again at a later time."

This is getting pretty tiresome. I have not had a single submission experience go well with this site.

Any ideas?

I am trying to beat the documentation change deadline of tomorrow. The app is all done and zipped up.....

Well, it took me 6 times but I finally got it submitted.
Break time....

Well, it took me 6 times but I finally got it submitted.
Break time....

What's the documentation change? I haven't heard of this.

What's the documentation change? I haven't heard of this.

Subject: New Test Guide Documents
A new version of the TRUE BREW Test Guide is now available on the BREW Developer Extranet. This version of the Test Guide will be incorporated into TRUE BREW Testing beginning Monday January 26, 2004. On that date, NSTL will cut over to the new version of the test guide. Applications submitted under the old test guide that are still in queue on the cut-over date will be tested and reported using the new test guide. Due consideration will be given to ensure that these applications are not unduly penalized (since these applications may have been submitted using the old test guide, yet will be tested using the new test guide). Applications submitted on or after the cut-off date must adhere to the new Test Guide.
The new Test Guide:
· Separates test requirements from test procedures, placing the procedures in a separate document (a spreadsheet).
· Adds camera and position location tests.
· Categorizes Errors that will cause an application to be Failed or Passed-with-Notes.
· Categorizes Issues that will be documented in a Test Report and may be considered by Operators when evaluating an application (even though the Issues will not cause the application to Fail nor cause it to be Passed-with-Notes).
· Requires developers to submit test results in the spreadsheet provided in the new Test Guide release.
The following documents are part of the new suite of test documents that should be used by BREW application developers submitting their applications for TRUE BREW Testing:
· TRUE BREW Process Overview (80-D4298-1 Rev. D)
· TRUE BREW® Test Guide (80-D4187-1 Rev. F)
· TRUE BREW® Test Procedures (80-D4187-3 Rev. A)
· TRUE BREW Application Specification Template (80-D4187-2 Rev. A)
The latter three documents are contained a single zip package.

Subject: New Test Guide Documents
A new version of the TRUE BREW Test Guide is now available on the BREW Developer Extranet. This version of the Test Guide will be incorporated into TRUE BREW Testing beginning Monday January 26, 2004. On that date, NSTL will cut over to the new version of the test guide. Applications submitted under the old test guide that are still in queue on the cut-over date will be tested and reported using the new test guide. Due consideration will be given to ensure that these applications are not unduly penalized (since these applications may have been submitted using the old test guide, yet will be tested using the new test guide). Applications submitted on or after the cut-off date must adhere to the new Test Guide.
The new Test Guide:
· Separates test requirements from test procedures, placing the procedures in a separate document (a spreadsheet).
· Adds camera and position location tests.
· Categorizes Errors that will cause an application to be Failed or Passed-with-Notes.
· Categorizes Issues that will be documented in a Test Report and may be considered by Operators when evaluating an application (even though the Issues will not cause the application to Fail nor cause it to be Passed-with-Notes).
· Requires developers to submit test results in the spreadsheet provided in the new Test Guide release.
The following documents are part of the new suite of test documents that should be used by BREW application developers submitting their applications for TRUE BREW Testing:
· TRUE BREW Process Overview (80-D4298-1 Rev. D)
· TRUE BREW® Test Guide (80-D4187-1 Rev. F)
· TRUE BREW® Test Procedures (80-D4187-3 Rev. A)
· TRUE BREW Application Specification Template (80-D4187-2 Rev. A)
The latter three documents are contained a single zip package.

Where is this new test guide--I don't see it.

Where is this new test guide--I don't see it.

Its on the page with the other developers docs:
https://brewx.qualcomm.com/bws/content/gi/brewdocs/TestGuideDocs.zip
I took a look at some of the new docs, and it looks like the main purpose is to add camera testing entries. However, there is a bit of an allusion that the 'passed with notes' criteria may change.
Since I have enough of a problem with cryptic, sometimes incorrect notes coming through, I figured I better push this app through now...

Its on the page with the other developers docs:
https://brewx.qualcomm.com/bws/content/gi/brewdocs/TestGuideDocs.zip
I took a look at some of the new docs, and it looks like the main purpose is to add camera testing entries. However, there is a bit of an allusion that the 'passed with notes' criteria may change.
Since I have enough of a problem with cryptic, sometimes incorrect notes coming through, I figured I better push this app through now...

Yeah I think I'll submit my new one under the new rules because I don't want the additional handset builds to fail after the first one just because of the doc change. Sounds like it's pretty much the same guidelines as they tested on before but they just actually document them instead of you getting surprise notes. :)

Yeah I think I'll submit my new one under the new rules because I don't want the additional handset builds to fail after the first one just because of the doc change. Sounds like it's pretty much the same guidelines as they tested on before but they just actually document them instead of you getting surprise notes. :)

BTW there's no spreadsheet in that zip--where's that at?

BTW there's no spreadsheet in that zip--where's that at?

All the docs are at:
https://brewx.qualcomm.com/brew/sdk/download.jsp?page=devrelations/brewd...
I don't see a spreadsheet either, perhaps its embedded in one of the word docs or pdfs.
"Yeah I think I'll submit my new one under the new rules because I don't want the additional handset builds to fail after the first one just because of the doc change"
Theoretically, their policy is one mod and one bar per submission, and a document change shouldn't mean an additional charge. However there is no means to do an add platform with documentation change, so I guess I would have to call them.
Shital is no longer there, so perhaps someone else from NSTL can clarify this.

All the docs are at:
https://brewx.qualcomm.com/brew/sdk/download.jsp?page=devrelations/brewd...
I don't see a spreadsheet either, perhaps its embedded in one of the word docs or pdfs.
"Yeah I think I'll submit my new one under the new rules because I don't want the additional handset builds to fail after the first one just because of the doc change"
Theoretically, their policy is one mod and one bar per submission, and a document change shouldn't mean an additional charge. However there is no means to do an add platform with documentation change, so I guess I would have to call them.
Shital is no longer there, so perhaps someone else from NSTL can clarify this.

I believe the new submission rules are favorable for developers, because they no longer require the Grinder and memory Shaker tests. The docs say this is temporary.

I believe the new submission rules are favorable for developers, because they no longer require the Grinder and memory Shaker tests. The docs say this is temporary.

Yeah from reading through these docs they just seem like they added new camera/gpos stuff and then documented all the undocumented errors that people were complaining about.

Yeah from reading through these docs they just seem like they added new camera/gpos stuff and then documented all the undocumented errors that people were complaining about.

I think the docs are also easier to write than the old ones, as you need to spend a lot less time describing product overviews, etc.
I did not notice that you had to send in the spreadsheet filled out. Where did you see that?

I think the docs are also easier to write than the old ones, as you need to spend a lot less time describing product overviews, etc.
I did not notice that you had to send in the spreadsheet filled out. Where did you see that?

From Jmiller's post:
"· Requires developers to submit test results in the spreadsheet provided in the new Test Guide release. "

From Jmiller's post:
"· Requires developers to submit test results in the spreadsheet provided in the new Test Guide release. "

haha...that is what caused me to ask the question! ;)
To clarify, where in the BREW submission docs does it detail what we specifically need to do for this?
-Aaron

haha...that is what caused me to ask the question! ;)
To clarify, where in the BREW submission docs does it detail what we specifically need to do for this?
-Aaron

Found it, there's an XLS in the TrueBrewTestProcedures.doc

Found it, there's an XLS in the TrueBrewTestProcedures.doc

Right, its test case 3.1.8. Any idea where "Appendix A" can be found? When naming, I suppose this file falls under:
Pre-testing test logs/reports: (appname_log.xxx)
-Aaron

Right, its test case 3.1.8. Any idea where "Appendix A" can be found? When naming, I suppose this file falls under:
Pre-testing test logs/reports: (appname_log.xxx)
-Aaron

Yeah back in ye olden days I used to just submit a word doc with every test case labeled and then pass or fail. (like 3.1.2: Pass) etc. etc.
So this is the same thign I just name it _log.xls

Yeah back in ye olden days I used to just submit a word doc with every test case labeled and then pass or fail. (like 3.1.2: Pass) etc. etc.
So this is the same thign I just name it _log.xls

Does it seem a little pointless to anyone to have developers fill this out? I suppose the "D" and "N" labels would be useful, but why would any developer put an "F" in a field? It seems that the spec template should cover all required "D" information.
-Aaron

Does it seem a little pointless to anyone to have developers fill this out? I suppose the "D" and "N" labels would be useful, but why would any developer put an "F" in a field? It seems that the spec template should cover all required "D" information.
-Aaron

I agree--although it's helpful to us because it forces us to read the test plan and make sure our app conforms. So I don't mind. I might actually catch something I forgot when going over the list.

I agree--although it's helpful to us because it forces us to read the test plan and make sure our app conforms. So I don't mind. I might actually catch something I forgot when going over the list.

Good point, but for my company the $1000 + $250(n-1) testing fee ensures proper pre-testing.
-Aaron

Good point, but for my company the $1000 + $250(n-1) testing fee ensures proper pre-testing.
-Aaron

I can't get the XLS sheet. Even though there is an icon on the Word document, there is no link associated with it in my version. On top of that the Extranet seems to be broken, asking me for my login over and over again when I access some of those docuemtns.
Can someone please send the XLS sheet to me real quick by email or PM so I can continue my work?

I can't get the XLS sheet. Even though there is an icon on the Word document, there is no link associated with it in my version. On top of that the Extranet seems to be broken, asking me for my login over and over again when I access some of those docuemtns.
Can someone please send the XLS sheet to me real quick by email or PM so I can continue my work?

Quote:Originally posted by Dragon
I can't get the XLS sheet. Even though there is an icon on the Word document, there is no link associated with it in my version. On top of that the Extranet seems to be broken, asking me for my login over and over again when I access some of those docuemtns.
Can someone please send the XLS sheet to me real quick by email or PM so I can continue my work?
I sent you one to your listed email.

Quote:Originally posted by Dragon
I can't get the XLS sheet. Even though there is an icon on the Word document, there is no link associated with it in my version. On top of that the Extranet seems to be broken, asking me for my login over and over again when I access some of those docuemtns.
Can someone please send the XLS sheet to me real quick by email or PM so I can continue my work?
I sent you one to your listed email.

Thanks for your help, guys. Very much appreciated.

Thanks for your help, guys. Very much appreciated.