apama.testplugin

Contains a PySys test plugin that provides a simple way to access Apama functionality from your testcases using self.apama.XXX().

ApamaPlugin

class apama.testplugin.ApamaPlugin[source]

Bases: object

PySys test plugin class for Apama, which provides access to Apama functionality from individual testcases.

To use this plugin make sure your project configuration contains:

<test-plugin classname="apama.testplugin.ApamaPlugin" alias="apama"/>

The members of this class will then be available to any test in the project using the “apama” alias i.e. self.apama.XXX. For example to call startCorrelator:

correlator = self.apama.startCorrelator('testCorrelator', ...)

New in version Apama: 10.7.0

TEST_EVENT_LOGGER_REGEX = '^[-0-9]* [0-9:.]* INFO .[0-9]*. - apama.test.TestEventLogger .[0-9]*. -- Got test event: (.*)'

The regular expression that identifies each event written to the correlator log by apama.correlator.CorrelatorHelper.injectTestEventLogger() and extracted using extractEventLoggerOutput().

antBuild(buildfile, **kwargs)[source]

Run an ant build file with Apama environment properties set, typically to generate a project artifact such as a Java plugin or adapter.

Runs in a ‘build’ subdirectory of the parent’s output directory.

Be careful to ensure that the ant build file generates its output under its working directory, or under an explicitly specified directory that is located inside the test output directory.

Parameters

  • buildfile (str) – absolute path to the ant build.xml to run

  • kwargs – Additional keyword arguments; see apama.build.antBuild() for details.

extractEventLoggerOutput(logFile)[source]

Uses log messages generated by apama.correlator.CorrelatorHelper.injectTestEventLogger() to extract a list of events from the specified correlator log file in a form that’s easy to manipulate from Python in your test’s validate() method.

Top-level events are each represented as a dictionary with an item for each event field, and a special key named .eventType whose value identifies the event type. Note that the order of the event fields is not preserved, however all dictionaries in the returned value will be sorted alphabetically by key to ensure consistent results.

This method is often used with pysys.basetest.BaseTest.assertThat, for example:

sensor1_temps = [ 
        # Extract only the field value(s) we care about (allows us to ignore unimportant information, timestamps, etc):
        (evt['temperature']) 
        for evt in self.apama.extractEventLoggerOutput('testCorrelator.log')

        # Filter to include the desired subset of events:
        if evt['.eventType']=='apamax.myapp.Alert' and evt['sensorId']=='TempSensor001'
        ]
self.assertThat('sensor1_temps == expected', sensor1_temps=sensor1_temps, expected=[
                111.0,
                120,
                145.2,
        ])

For debugging purposes, a readable multi-line JSON representation of the events is logged when run using:

pysys run -v assertions.apama=debug
Parameters

logFile (str) – The path of the correlator log file containing the logged events.

Returns

A list[dict[str,obj]] where each item is a dictionary representing the fields of an Apama event.

projectHelper(projectName, **kwargs)[source]

Create a new instance of the apama.project.ProjectHelper class that can be used for creating, manipulating and deploying Apama project directories.

Parameters

  • projectName (str) – The project directory.

  • kwargs – Additional arguments to be passed to the apama.project.ProjectHelper constructor.

Returns

An instance of apama.project.ProjectHelper.

startCorrelator(name='testCorrelator', arguments=[], java=None, Xclock=False, config=None, **xargs)[source]

Start a new correlator process on a dynamically allocated port, and wait until it is running.

Parameters

  • name (str) – A logical name for this correlator, which will be used for the log filename, stdouterr and the component name.

  • java (bool) – If True then the correlator will be started with support for injecting Java applications.

  • Xclock (bool) – If True then the correlator will be started in externally clocked mode, meaning that time is controlled by sending in &TIME(...) ticks from a .evt file rather than from the system clock.

  • config (list[str]|str) – path or list of paths to a initialization or connectivity configuration .yaml file or directory containing them.

  • arguments (list[str]) – Additional arguments to be passed to the correlator.

  • xargs – Additional keyword arguments that will be passed to apama.correlator.CorrelatorHelper.start().

Returns

An instance of apama.correlator.CorrelatorHelper that you can use to interact with your application.

startIAF(name, configname, **xargs)[source]

Start a new IAF (adapter) process on a dynamically allocate port, and wait until it is running.

Parameters

  • name (str) – A logical name for this IAF process, which will be used for the log filename, stdouterr and the component name.

  • configname (str) – The IAF configuration file or template name

  • xargs – Additional keyword arguments that will be passed to apama.iaf.IAFHelper.start().

Returns

An instance of apama.iaf.IAFHelper.