XQuery Question:
What does compatibility testing involve and who will do the testing?
Answer:
Third-party testing labs will conduct the compatibility testing. Exactly what will be tested will differ from application to application, but generally, testing will cover the following:
► How the application interacts with core phone functionality. For example, how the application handles scenarios such as an instant message or other system alerts being pushed to the device while the user is in another application.
► Core application stability over time. Numerous events will be sent into the event queue to see how the application handles them and to look for instability (i.e. crashes), memory usage (i.e. leaks), etc.
► Major application functionality. Testing will be conducted to make sure the major functionality you claim for your application actually is in the application. Qualcomm will not test this functionality for "correctness" from an end-user perspective.
► A standard set of tests for each area of BREW functionality used by the application. For example, we will use a standard file system test suite if the application uses the BREW file system calls. Similarly, if an application uses the BREW networking calls, we will test this with a standard networking test suite.
► Any operator or manufacturer-specific look and feel requirements.
► Compatibility with the target device(s).
► Interaction with required accessories.
► How the application interacts with core phone functionality. For example, how the application handles scenarios such as an instant message or other system alerts being pushed to the device while the user is in another application.
► Core application stability over time. Numerous events will be sent into the event queue to see how the application handles them and to look for instability (i.e. crashes), memory usage (i.e. leaks), etc.
► Major application functionality. Testing will be conducted to make sure the major functionality you claim for your application actually is in the application. Qualcomm will not test this functionality for "correctness" from an end-user perspective.
► A standard set of tests for each area of BREW functionality used by the application. For example, we will use a standard file system test suite if the application uses the BREW file system calls. Similarly, if an application uses the BREW networking calls, we will test this with a standard networking test suite.
► Any operator or manufacturer-specific look and feel requirements.
► Compatibility with the target device(s).
► Interaction with required accessories.
| Previous Question | Next Question |
| What should I do if installation fails when trying to install a Java™ Verified application to an S60 device? | What is the purpose of compatibility testing? |