The standard oat module tests the API interfaces defined in brew, which guarantees the consistency of brew in cross-platform migration. Mobile phone manufacturers may develop their own brew Application Extensions based on the characteristics of their respective mobile phones. These Application Extensions may be effective on all or some mobile phone platforms of the mobile phone manufacturers, in this case, mobile phone manufacturers need to customize their own oat modules to ensure the correctness and consistency of these extension classes.
Through oat-based custom testing, mobile phone manufacturers can use the OAT testing framework to verify their own extended functions. The oat custom modules can be reused on different mobile phones to improve work efficiency. Because the customized testing of oat provides certain quality assurance, BREW application developers can also safely use the features provided by mobile phone manufacturers for a series of mobile phones, to develop ingenious applications and services.
Mobile phone manufacturers can use the OAT development tool (odk) to develop their own oat custom modules. Because odk does not need the support of the brew porting tool kit (PK, in principle, application developers can also use odk to test their own extended applications.