Presentation were given at JavaOne 2010

2. Optimizing Java Device Testing with Automatic Feature Discover y Fyodor Romanov, Software Engineer

4. Testing framework structure.

5. Approach how to optimize and shorten device test-cycle using Diagnostic tests to explore device capabilities.

6. Demo showing Diagnostic tests usage and benefits

7. Problem description

9. Before a manufacturer can make a device commercially available, they must perform a significant amount of testing to ensure a high-quality, reliable product that delivers customer satisfaction.

10. Java Device quality testing helps Java technology wireless device manufacturers and network operators maximize product quality and minimize time to market.

11. Problem description There are a lot of (more then 30) Java Platform, Micro Edition (Java ME platform) technologies (and combinations):

13. Up to 3 weeks for guru to run all test on one device.

14. Challenge of managing and, if possible, lowering quality testing costs.

15. The most challenging task for test execution is to configure tests for particular device.

16. Express testing: evaluate device quality in 4 hours.

18. Problem statement Device manufacture knows, but testing house doesn't.

19. Before Automatic feature discovery.

20. Solution in nutshell

21. Solution implementation

22. Solution implementation Implementation example will be based on JDTF test framework however it should be applicable to any Java device testing framework. The Java Device Test Framework (JDTF) is a test framework based on Oracle‘ s commercial Java Device Test Suite (JDTS) product. JDTF is a general purpose, fully-featured, flexible, and configurable test framework suited to assess various aspects of Java Platform, Micro Edition (Java ME) device implementation quality .

23. JDTF overall tests structure JDTF organizes tests into hierarchical structure s called test packs , a collection of tests that are functionally related and have common setup requirements :

24. JDTF testing structure Harness is using tests and different configuration files to execute test on device. Test execution on device is controlled by MicroAgent which starts/stops test and communicates with Harness (sends results, logs, etc.)

25. Tests execution workflow

27. Move them into special dedicated test pack.

28. Writing diagnostic test. Changes in MicroAgent. Diagnostic tests find out whether the device supports an optional feature and export a property by using Logger class as follows. public class Logger { ... public void exportProperty(String name, String value) { LogRecord rec = new LogRecord (...); rec.setProperty(EXPORTED_PROPERTY_PREFIX + name, value); ... } }

30. Test should be marked with ‘diagnostic’ keyword

31. Test should try to use optional feature and call Logger.exportProperty(String name, String value)

32. If feature is supported, return PASSED and if feature is not supported return FAILED. This helps to visualize test result.

33. Do nothing else

34. Writing diagnostic test. Code Sample. public class ConnectionTest implements AutomatedTest { ... public boolean testHTTP() { Connection c = null; try { ... c = Connector.open(url); logger.exportProperty("HTTPSupport", "true"); return true; } catch (IllegalArgumentException iae) { return false; } ... }

35. Developing Template Generator

36. Adding Template Builders to TestPacks

37. Changes in FW

38. Final touch. Adjusting Relevance Filters Relevance filter should filter out not relevant test providing right reason. Code sample: public String LapiDependencyProvider.isRelevant(final TestId id) throws TestDependencyProviderException { final boolean createDeleteLmsSupported = getBoolean(TestPackProperty.CreatingAndDeletingLandma rkStoresSupported, id); if (!createDeleteLmsSupported) { if (fqn.endsWith("#addLandmarkScenario2") || fqn.endsWith("#deleteLandmarkFromAnotherLMS") { return "Test not relevant because Landmark Store create/delete operations configured to be not supported."; } }

40. Reduces 1 - 2 days work for one person (depending of person's experience) to 30 minutes.

41. Before Automatic Feature Discovery feature customers were taking a complete unknown device and painstakingly reading logs to find out what it supports .

42. DEMO

44. JDTS home page with API detailed description

45. http://www.oracle.com/technetwork/java/javadevice-140362.html

47. How to process Diagnostic tests output in testing framework JDTF test framework was used for demonstration <Insert Picture Here>

48. Q&A Q&A