logo logo

TestProject SDK (v1) vs. OpenSDK (v2)

Recently, we’ve released a completely new and open source SDK (v2) with PythonJava and C# bindings, named OpenSDK. The philosophy behind OpenSDK is to have a single SDK that is as close as possible to the standard Selenium and Appium we all know and 💗, allowing users to easily integrate it into existing automation frameworks, while utilizing TestProject’s Agent power for: driver management, single click configuration and automatic reporting features.

When working with the OpenSDK to develop and execute Web, Android or iOS tests, all that is required to have a completely managed Selenium/Appium experience is an installation of the TestProject Agent, and that’s it!

  1. Save time & effort of downloading different Selenium drivers or configuring Appium. Everything is handled automatically by the TestProject Agent.
  2. You can use any framework or 3rd party tools: Unit testing frameworks, Cucumber, SpecFlow, Junit, TestNG, etc.
  3. No need to upload anything to the TestProject Cloud or integrating reporters of any kind.
  4. You will benefit from beautiful test reports that are automatically created for you on TestProject’s reporting dashboard, where you will be able to also download them in PDF format.

What About the Standard SDK (v1)?

SDK v1 allows you to package and upload your binaries (C# DLL/Java JAR files) to TestProject’s cloud platform as “Coded Tests”. From that moment, TestProject is responsible for distributing and deploying your tests across multiple Agents. Although SDK v1 is based on Selenium and Appium APIs as well, it uses additional layers of interfaces for supporting the automatic distribution. Thus, users who have existing frameworks may require extra effort adjusting it.

TestProject SDK (v1) vs. OpenSDK (v2) – Summary

Below is a short summary of the key differences between TestProject SDK (v1) vs. OpenSDK (v2):

Feature

TestProject SDK (v1)

OpenSDK (v2)

Selenium driver management for all browsers

Supported

Supported

Appium driver management for iOS and Android

Supported

Supported

Support for iOS on Windows

Supported

Supported

Usage within existing automation framework

Requires some Effort

Seamless Support

Automatic step execution reporting

Not supported

Supported

Local execution with automatic reporting

Only for C#

Supported

C# Support

Supported

Supported

Java Support

Supported

Supported

Python Support

Not Supported

Supported

Automatic deployment and execution

Supported

Not yet Supported [1]

WebDriver custom capabilities

Not Supported

Supported

Conclusion

If you are utilizing the upload code feature and coded tests deployment by TestProject platform – then SDK v1 is for you. However, if you are looking to enrich your existing platform with the power of automatic reporting and driver management, while having a flexible framework with your own build and deployment pipelines (while storing the artifacts locally) – you should probably try the OpenSDK (v2).

Meital Matsafi

About the author

Meital Matsafi

As the Head of Community at TestProject and a test automation enthusiast by ❤, I love building and maintaining relationships with our community members, diverse community organizations, and internal entities while learning and sharing my key findings. Assisting with the development of robust engagement plans & activities I’m extremely eager to evolve and grow the community.

Join TestProject Community

Get full access to the world's first cloud-based, open source friendly testing community. Enjoy TestProject's end-to-end test automation Platform, Forum, Blog and Docs - All for FREE.

Join Us Now  

Leave a Reply

popup image

A new world for test automation

Join 150,000 testing & dev teams taking their web & mobile testing to new heights, using #1 FREE test automation platform, designed to help deliver quality at speed.
Get Started
FacebookLinkedInTwitterEmail