|
||||||||||||||||||||||||||||||
|
|
Testing and signing your mobile apps is an important part of the development cycle which can be expensive for some.
step 1: Quality Assurance testing
step 2: Orange acceptance testing
step 3: signing
Please note that this is for Orange distribution only, so we won’t give you back a signed version or the test report. However, we will tell you about any failures, if any. Quality Assurance (QA) testing begins when you have finished creating your code and you need to test that your application works on devices.
Usually you’ll develop one or two (sometimes more) reference builds first. These reference builds should be QA tested thoroughly by you - the developer - before porting any further variants to suit particular handset families. See Java Verified for Java handset families
Don’t worry, help is it hand We can provide technical support that can help in different stages of your development. Find some of these below…
Getting hold of devices is vital to successfully carrying out QA testing. To help you with this, you can phyisically visit one of our developer centres in:
Each centre offers a well-equipped technical facility with mobile devices with Orange SIMs, 2G and 3G Orange network,Wifi internet connection and meeting rooms.
Learn more about Orange developer centres and book your place
Learn more about Orange virtual developer centre and access it
We have several tools and guidelines to help you with the development and testing phases of your app.
Once you’re happy with your QA tests, the next stage of the testing process is Once we determine an interest in your application and you’ve carry out your QA testing - only then does formal testing start on our part, this is Orange acceptance testing.
We will test your application according to a set of criteria appropriate to:
If you fail the acceptance testing, you need to fix it and re-submit the builds. Please note that we will not do QA testing for you. If you have a long standing history of providing us with high quality applications or games then ….
Testing criteria per platform: Java
![]() We will pay to test your application to the Java Verified standard using the test criteria (Unified Test Criteria).
This is for Orange distribution only, so we won’t give you back a signed version or the test report. We will tell you about any failures. You can test your application for yourself using these criteria to understand what we will test. We run a different set of tests for simple applications compared to complex connected applications.
Optional step If you want to prove to us that your application is high quality. Take one reference build of your app through Java Verified (a cost of $200 per build to you, and you need a Publisher ID costing $200 per year). Show us that it has passed (include the test report) and we’ll be able to fast track your app through testing. This also gives you a fast track passport to many other operators and manufacturer stores. Remember, this is an optional step and entirely your choice. All Symbian applications must be express signed - we cannot do this for you (express level is the minimum. Some features require more). You will need a Publisher ID (cost $200 for a year) and express signing costs $20 per signing.
We use mobile to market standards. We will take care of the signing for you.
We use RIM/Blackberry standards. We are working with RIM towards a common acceptance standards.
As there are no formal industry standard testing criteria for Android apps at the moment, we'll carry out testing on a case by case basis.
|
|
||||||||||||||||||||||||||||