cc636fff21
This is a complete redesign of what was previously XmppNioTcpConnection. The new architecture allows to extend an XMPP client to server (c2s) connection with new transport bindings and other extensions.
8.5 KiB
Smack's Integration Test Framework
Introduction
Smack's Integration Test Framwork is used to run a set of tests against a real XMPP service. The framework discovers on startup the available tests by reflection.
Quickstart
You can run the framework against an XMPP service with
$ gradle integrationTest -Dsinttest.service=my.xmppservice.org
Note that the service needs to have In-Band Registration (IBR) enabled.
A better alternative to IBR is using XEP-0133: Service Administration to create the throw away accounts used by the integration test framework. Simply use
$ gradle integrationTest -Dsinttest.service=my.xmppservice.org \
-Dsinttest.adminAccountUsername=admin \
-Dsinttest.adminAccountPassword=aeR0Wuub
to run Smack's integration test framework against my.xmppservice.org
with an admin account named admin and aeR0Wuub as password.
Configuration
The framework is configured with a standard Java properties file.
This file simply contains key/value pairs, which are separated by an equals sign ("=").
The most important configuration value is the service value, it's also the only required setting.
The file properties can be overridden with Java system properties.
The name of a system property that is used by the framework needs to be prefixed with sinttest. (Smack Integration Test Framework).
For example the service property becomes sinttest.service.
Minimal example properties file
service=example.org
Another example properties file
service=example.org
serviceTlsPin=CERTSHA256:2F:92:C9:4D:30:58:E1:05:21:9A:57:59:5F:6E:25:9A:0F:BF:FF:64:1A:C3:4B:EC:06:7D:4A:6F:0A:D5:21:85
debugger=console
Framework properties
| Name | Description |
|---|---|
| service | XMPP service to run the tests on |
| serviceTlsPin | TLS Pin (used by java-pinning) |
| securityMode | Either 'required' or 'disabled' |
| replyTimeout | In milliseconds |
| adminAccountUsername | Username of the XEP-0133 Admin account |
| adminAccountPassword | Password of the XEP-0133 Admin account |
| accountOneUsername | Username of the first XMPP account |
| accountOnePassword | Password of the first XMPP account |
| accountTwoUsername | Username of the second XMPP account |
| accountTwoPassword | Password of the second XMPP account |
| accountThreeUsername | Username of the third XMPP account |
| accountThreePassword | Password of the third XMPP account |
| debugger | 'console' for console debugger, 'enhanced' for the enhanced debugger |
| enabledTests | List of enabled tests |
| disabledTests | List of disabled tests |
| defaultConnection | Nickname of the default connection |
| enabledConnections | List of enabled connection's nicknames |
| disabledConnections | List of disabled connection's nicknames |
| testPackages | List of packages with tests |
| verbose | If true set output to verbose |
Where to place the properties file
The framework will first load the properties file from ~/.config/smack-integration-test/properties
Overview of the components
Package org.igniterealtime.smack.inttest
SmackIntegrationTestFramework
Contains public static void main method, i.e. the entry point for the framework.
Here the available integration tests are discovered by means of reflection, the configuration is read and a IntegrationTestEnvironment instance created, which includes the XMPPConnections.
AbstractSmackIntegrationTest
The base class that integration tests need to subclass.
AbstractSmackLowLevelIntegrationTest
Allows low level integration test, i.e. ever test method will have its on exclusive XMPPTCPConnection instances.
AbstractSmackSpecificLowLevelIntegrationTest
Operates, like AbstractSmackLowLevelIntegrationTest on its own XMPPConnection instances, but is limited to a particular type of XMPPConnection.
IntegrationTestEnvironment
The environment, e.g. the XMPPConnections provided to the integration tests by the framework. Note that for convenience AbstractSmackIntegrationTest contains some of those as protected members.
SmackIntegrationTest
An annotation that needs to be added to all methods that represent a single integration test. Annotated integration test methods must not take any arguments (i.e. their parameter count is 0), and should return void as it's not evaluated in any way. The methods are supposed to throw an exception if their integration test fails.
TestNotPossibleException
Can be thrown by test methods or constructors to signal that their test it no possible, e.g. because the service does not support the required feature.
Running the integration tests
Smack's Gradle build system is configured with a special task called integrationTest, which means you can run the tests simply with
$ gradle integrationTest -Dsinttest.service=my.xmppservice.org
If one of accountOneUsername, accountOnePassword, accountTwoUsername or accountTwoPassword is not configured, then the framework will automatically create the accounts on the service. Of course this requires account registration (IBR) to be enabled.
If the accounts got created automatically by the framework, then they will also be deleted at the end of the test.
Implementing Integration Tests
Create a new class which extends AbstractSmackIntegrationTest.
Every non-static method, including the constructor, of this class will have two XMPPConnections available to perform the integration tests with: conOne and conTwo.
You can use the constructor to check if the XMPP service does provide the required XMPP feature.
If it does not, simply throw a TestNotPossibleException.
Test methods must be public, take zero arguments i.e. declare no parameters and be annoated with @SmackIntegrationTest.
If the test method is not able to perform a test then it should throw a TestNotPossibleException.
Rules for integration tests
Tests should not leave any traces on the service if they are finished, i.e. the service state at the end of the test must be equal to the state of the beginning. It must be possible to run the tests in parallel.
Why are there two mechanisms to signal that the test is not possible?
Because the XMPP service may provide a component that is required to perform a certain integration test, but that component may not support all features. For example, the XMPP service may provides a PubSub (XEP-0060) component, but this component may not support all features of XEP-0060.
Low-Level Integration Tests
Classes that implement low-level integration tests need to sublcass AbstractSmackLowLevelIntegrationTest.
The test methods can declare as many parameters as they need to, but every parameter must be of type XMPPTCPConnection.
The framework will automatically create, register and login the connections.
After the test is finished, the connections will be unregistered with the XMPP service and terminated.
Running your own integration tests
The framework can be used to run your own tests residing outside of the framework's default package scope.
Simply set the testPackages property to a comma separated list of package names where the framework should look for integration tests.
Example:
$ gradle integrationTest -Dsinttest.service=my.xmppserivce.org -Dsinttest.testPackages=org.mypackage,org.otherpackage