Installation
Add the SDK package for the language used by your test project.
Java
Before you begin, ensure that the project uses Java 8 or later and Maven 3.6 or later.
Add the dependency to pom.xml:
<dependency>
<groupId>io.testinium.devicepark</groupId>
<artifactId>device-park-public-sdk</artifactId>
<version>1.0.1</version>
</dependency>Version 1.0.1 uses the API contracts documented in this guide. Projects that already obtain the artifact from their configured repository do not need a custom repository block.
If your environment cannot access Maven Central and your organization delivers the SDK as a JAR, install that exact artifact into the local Maven cache:
mvn install:install-file \
-Dfile=/path/to/device-park-public-sdk-1.0.1.jar \
-DgroupId=io.testinium.devicepark \
-DartifactId=device-park-public-sdk \
-Dversion=1.0.1 \
-Dpackaging=jarThen use the same dependency block above. Repository mirrors and offline artifact delivery are organization-specific and are not part of the SDK runtime configuration.
Java SDK 1.0.1 uses the io.testinium.devicepark package namespace. Replace older com.devicepark.sdk imports when upgrading.
Upgrade from the Previous Java Coordinates
Contract | Previous | Current |
|---|---|---|
Maven groupId | com.devicepark | io.testinium.devicepark |
Maven artifactId | device-park-public-sdk | device-park-public-sdk |
Java package root | com.devicepark.sdk | io.testinium.devicepark |
Use io.testinium.devicepark:device-park-public-sdk:1.0.1 and update both the Maven groupId and Java imports.
Node.js
Before you begin, ensure that Node.js 18 or later is installed.
Install the package:
npm install @device-park/public-sdkFor a package delivered as a tarball:
npm install /path/to/device-park-public-sdk-1.0.1.tgzIf the package version is not yet available from your configured npm registry, obtain the release tarball from your Device Park administrator. Do not commit registry tokens or package files containing credentials.
The package uses ES modules. Use import syntax in Node.js examples.