IntegrationsTests

Introduction

Building the system might cause difficulties and it's unclear if the flashed test device contains a fully integrated SmartCard API with proper Secure Element access.
When using the patches together with the Mobile Security Card it's unlikely to expect different behaviors but for OEMs that adapt the RIL interface towards the baseband it's required to provide a test tool to ensure the overall system integration.
We need to split the test setup in different scenarios, like

• SmartCard API system tests
• Access control scheme tests
• CTS conformance tests

Part1: Performance tester

The PerformanceTester is a tool suitable for system integrators or developers who need to verify that the SmartCard API integration was successful and the access to the Secure Element is working.

• Download and extract the PerformanceTester

• The package contains:

  • PerformanceTester.apk: The Android application
  • PerformanceTester.cap: JavaCard applet that must be downloaded into the SE as counterpart by using JLoad or similar tools

• PerformaceTester runs all APDU test cases - case-{1,2,3,4} commands - with all possible command and response length in a predefined loop

• The application determines the performance characteristics of the SmartcardAPI:

  • Time measurement of APDU communication
  • CPU usage of the SmartcardAPI
  • Memory consumption of the !SmartCardAPI
  • Energy consumption during the test

• Features

  • Each APDU during the test will be verified for correctness.
  • Configuration of the APDU generator to define a test run.
  • Selection of the SE (the counterpart of this test application)
  • Selection of the communication channel
  • Generation of a test report
  • Real time view for observing the communication

Note: PerformanceTester relies on the SmartCard API integrated in the Android platform. Thus, MSC SmartcardService version 1.5 will not work.