Installation

Add the SDK package for the language used by your test project.

Before you begin, ensure that the project uses Java 8 or later and Maven 3.6 or later.

Add the dependency to pom.xml:

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:

Then 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.

Use io.testinium.devicepark:device-park-public-sdk:1.0.1 and update both the Maven groupId and Java imports.

Before you begin, ensure that Node.js 18 or later is installed.

Install the package:

For a package delivered as a tarball:

If 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.

Before you begin, ensure that the project targets one of the supported frameworks listed below.

Install the package:

Or add it to the project file:

The assembly and root namespace are Testinium.DevicePark:

The package ships three assets and resolves the closest one automatically.

.NET Framework 4.6.1 satisfies netstandard2.0, but it defaults to SSL3 and TLS 1.0 and therefore cannot complete an HTTPS request to Device Park unless the host application changes ServicePointManager.SecurityProtocol. Use 4.7.2 or later, where the operating-system default applies.

The SDK has no package dependencies on any target framework. Installing it adds one assembly and nothing else, including on .NET Framework. It also takes no dependency on any host or dependency-injection container.

If your environment cannot reach nuget.org and your organization delivers the SDK as a .nupkg file, add a local folder feed:

Do not commit NuGet API keys or package files containing credentials.

Create an authenticated SDK client.