Jython for Embedded Software Validation
- 1. Jython for Embedded Software ValidationRaniero VirgilioIAG/ECG/PPD SW Pycon Quattro, 8/5/2010
- 2. Raniero VirgilioMy Job Software Engineer in Intel Shannon, IrelandResponsible for Test Automation infrastructureMy TeamPPD (Performance Product Division)Embedded SoftwareComplete SOCs for security, communications, storage and embedded designshttp://www.intel.com/embedded/index.htm
- 3. AgendaValidation in embedded systemsRuntime Plug-in modelRuntime Plug-in model with JythonJython and EclipseResults
- 4. Validation in embedded systemsA challenging environmentTypical scenarioRequirements and solutions
- 5. A challenging environmentMultiple hw/sw deploymentsConfiguration set up needs to be fast and reliableSupport for different OS types and versionsConsistent cooperationSeveral teams working on the same infrastructureSynchronization with overseas groups
- 6. Test Automation scenarioTest CodeXML-RPC sessionServer1 (Windows)Traffic Generator 1XML-RPC sessionTraffic Generator 2Server2 (Windows)Telnet sessionTest DriverDUT1 (Linux/Windows/FreeBSD)Test ExecutionReportsXML-RPC sessionTelnet sessionTest SuitesDUT2(Linux/Windows/FreeBSD)Telnet sessionDUT3(Linux/Windows/FreeBSD)
- 7. Test Automation requirementsProgramming languagePlatform-independentLibraries for connectivity and string manipulationTest Framework designOOP to maximize reusability of test codePlatform runtime extendibilitySustainable implementationAn effective interface between test execution (local to DUT) and test reporting (distributed)Customizable open source solution
- 8. Proposed solutionProgramming languagePythontelnetlib, xmlrpclib, SimpleXMLRPCServerre,xml.dom.minidomTest Framework designRuntime plug-in modelSustainable implementationJython embedded in EclipseJython is a Python interpreter written in 100% pure Java
- 9. Runtime plug-in modelDefinitionDesign Pattern
- 10. Runtime Plug-in ModelThe term plug-in refers to a type of program that contributes code to the system and adds a special capability to it.The plug-in is unknown at compile-time of the application for which the plug-in is designed.Plug-ins are dynamically plugged into the application they are designed for at runtimeThe key for this model is Dynamic Code Loading
- 12. Application capabilities are defined by the supported Plug-in
- 13. Plug-in can be loaded and unloaded at runtime
- 15. Each Plug-in shall implement a specified interface
- 16. The plug-in delegates the Application for high-level services
- 18. Application and Plug-ins can be developed independently Runtime Plug-in Model with JythonDynamic code loading in Java and JythonMultithreading
- 19. Dynamic code loading in JavaRuntime source compilation
- 20. StandardJavaFileManager handles the source code
- 21. JavaCompiler executes the compilation and creates a class file
- 22. DiagnosticCollector gathers compilation information
- 24. A new Classloader has to be defined
- 25. It need to extend the previous one with the new class fileClient
- 26. Dynamic code loading in JythonOne step task
- 27. The PluginHandler instantiates one PythonInterpreter
- 28. The Plug-in path is added in the PythonInterpretersys.path
- 29. The Plug-in is imported in the embedded Python environment
- 30. Lower complexity
- 31. Implementation is much easier
- 32. Code can be modified “on-the-fly” and reloaded
- 33. First time Plug-in loading is usually quicker on JythonClient
- 35. Independent Jython environments’ setups
- 36. Each PluginHandler defines an autonomous environmentJava ThreadMultiple task execution
- 37. When PluginHandler invokes a run() the execution is encapsulated in a Java Thread
- 38. Plug-ins expand the application concurrentlyClient
- 39. Jython and EclipseXTP architectureThe Execution EnginesThe JythonExchanger
- 40. The eXtendible Test Platform (XTP)JavaJython
- 41. The Execution Engine in XTPXTP
- 42. provides high-level test services (logging, reporting, multithreading) and an interface with frontend
- 43. Execution Engine
- 44. a self-contained software package, written in Python, that implements the actual test logic and expands XTP enabling communication of the test platform with DUTs, servers and test equipmentsPlugging an Execution EngineXML-based ManifestjythonExchangerA PythonInterpreteris created by XTP
- 45. The activation sequences contained in the EE Manifest are executed in the PythonInterpreter
- 46. An instance of the (Java) JythonInterpreter class is created by XTP and deployed into the relevant PythonInterpreterThe jythonExchangerThe jythonExchanger is the interface between the EE and the XTP environment
- 47. Each EE uses it to access XTP high-level features
- 48. XTP infrastructure uses it to retrieve test results from EEs and show them in graphs and reports
- 49. The overall consistency of the system is assured by the Jython characteristic to be a 100% pure Java implementation. ResultsMain benefitsCommon risks
- 50. Sustainable architectureExample: load/unload 5 plug-ins at runtime
- 51. Memory request increases without “exploding”
- 52. Memory is freed when plug-ins are deactivatedMajor benefits“Calibrate your technology”Choose the solution that best fits your needsPython threads or Java threads (or Eclipse Jobs)? Transparent Python layer on DUTsXML-RPC Server + os.popen() have small CPU overheadPlug-in lifecycleRuntime plug-ins promote validation through cooperationShort rump-up timePerl users start using Python very intuitively
- 53. Common risks“Design your architecture”Test planningTo make the most of the Plug-in design pattern, point out common test domains in advanceLong-term investmentPlatform stability requires a significant effortKeep code under controlReview carefully test code before integrating itRight-Size your hardwareConcurrent executions may require performing machines
- 54. Q&A