External interfaces

While the Card Conformance Tool (CCT) offers both a graphical user interface (GUI) and a command line interface (CLI), not all operations are available from the CLI. Some test configuration operations may either require you to use the GUI or manually edit a configuration file.

You can use the CLI to execute preconfigured sets of tests headlessly. In other words, you can execute tests without interacting with the GUI.

Graphical User Interface (GUI)

The CCT GUI resembles an Integrated Development Environment (IDE) used for software development. The GUI provides functions for creating and editing Card Conformance Test Set (CCTS) documents. These documents contain the following:

• Test selections
• Test configurations
• Test run history with results
• Reports generated

You can use the GUI to perform the following tasks:

• Alter the selected set of tests
• Edit configurable parameters for the tests
• View the test run history
• Clear the test run history
• View test reports
• Export test reports
• View and filter test logs
• Export and see filtered views of test logs
• Configure logging settings for both GUI tool operation and test execution
• Execute tests with a progress display

Command Line Interface (CLI)

The CCT command line executes tests in an existing CCTS document, as configured by the CCT GUI. You can use the CLI to configure logging settings using textual properties files (which may be prepared in the GUI) and store the results of the test runs either in the CCTS document or in a copy of the CCTS document, as determined by arguments supplied on the command line.

The CLI also offers the ability to export test reports from test runs within a CCTS document.

CCTS Documents

CCTS documents are SQLite 3 databases. You can manipulate these using the GUI and command line interfaces, but the end-user documentation includes a schema for these databases to facilitate manipulation using standard commercially available SQLite tooling.