Brew advanced and proficient-3G mobile value-added business operation, customization and development-95-brew typical examples include testing TBT

Commercial tests for brew applications generally refer to TBT, that is, true brew test. The purpose of TBT is to ensure that the operator's network provides mobile value-added services that are virus-free, malicious, and stable. TBT is a set of test requirements and test processes used to test and evaluate a mobile value-added service. For example, you can use a mobile phone or commercial network to test the performance of applications on a real mobile phone. TBT reduces the complexity of application testing. For example, different mobile phone platforms and mobile phone software versions can help developers improve application quality, especially for new developers.

As a typical service provided by registered developers, TBT provides various carrier-specific testing processes based on TBT and their own needs. Many operators use TBT as an independent test process and increase or decrease the test scope of TBT. TBT adds a business opportunity for commercial applications on networks of multiple carriers, as shown in a typical TBT Testing Process of 16-10.

TBT testing is actually a process of testing software according to a series of requirements of ntsl. It consists of seven parts:

In the first part, the product must meet the entry criteria before testing is allowed,

Part 2. "exploratorytesting" (test)

Part 3: test the plug-in devices such as headphones

Part 4: functional tests on BREW, including network, voice calls, and text messages.

Part 5 brew's New User Interface Test

Human-Machine Interaction Test

Part 7 Application download Test

The scope of TBT is 16-11.

 

TBT has four types of test: complete test, platform test, spot check test, and inheritance test. For a complete test, all test cases must be executed for the applications provided by CP/SP, mainly for applications submitted by application developers. If an application of the application developer has passed the TBT test on a mobile phone platform and hopes that the application can also be commercially available on another mobile phone platform, you need to transplant the platform for testing. In the porting platform test, the application code, including the resource file, remains the same as the code file and resource file on the mobile phone platform that uses TBT. Therefore, only the test case of the exploratory test is executed. Spot check test allows the application developer to modify the resource files of the application, the MIF file, and all other files except the MOD file. Only a limited number of test cases need to be executed during spot check test.

The inheritance test is mainly initiated by mobile phone manufacturers, and application developers do not need to participate directly. The inheritance test mainly relies on the inheritance tree of mobile phone manufacturers. For example, the mobile phone manufacturer XXX first listed a mobile phone A, which serves as the root node of the parent phone in the mobile phone inheritance tree. Currently there are 68 value-added services based on BREW mobile on mobile phone, then, the mobile phone manufacturer XXX first listed a mobile phone B, which fully covered the performance of mobile phone A and provided new features, then, you can use mobile phone B as the child node of mobile phone A in the inheritance tree. In this case, you can test the inheritance application, all 68 applications on mobile phone A can be commercially used on mobile phone B. If you have performed an inherited application test, you only need to perform a limited number of test cases.