Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 46 Next »

This plugin integrates SOASTA CloudTest and SOASTA TouchTest features into Jenkins.

Plugin Information

View SOASTA CloudTest on the plugin site for more information.

The current version of this plugin may not be safe to use. Please review the following warnings before use:

The CloudTest Jenkins plugin provides the ability to

  • Easily run the MakeAppTouchTestable utility on an iOS or Android project
  • Silently install an iOS app on a connected device
  • Play CloudTest compositions and include the output in the build's test results

Prerequisites

The CloudTest plug-in requires Jenkins 1.447 or later.

Global Configuration Options

Before using the plug-in, you will need to provide the CloudTest server information, in the "Manage Jenkins" -> "Configure System" page. This includes the CloudTest URL and a set of credentials. We recommend creating a dedicated CloudTest account for Jenkins to use.

The CloudTest password is encrypted before saving it to disk. It is also masked (e.g. "****") in all output generated during builds.

Build Steps

The plug-in adds the following new build steps:

Make App TouchTestable

Adds the TouchTest Driver library to your app's source code. Typically this build step is inserted right before the build step that compiles the app's code (e.g. before the Xcode build step for iOS, or before the "Invoke Ant" build step for Android).

Install iOS App on Device

Silently installs an IPA file on one or more attached iOS devices. This ensures that your tests run against the latest version of your app.

Note: there is no Android version of this build step, because the Android SDK already provides this functionality ("adb install").

Play Composition

Executes a CloudTest composition, and saves the output in the build's test results. You can include this build step multiple times if there are multiple compositions in your test suite.

Wake Up iOS Device

Wakes up one or more attached iOS devices, and opens Mobile Safari to the most recently-viewed page (e.g. TouchTest Agent). This can optionally be used at the beginning of a build, to "prep" the devices for testing.

Note: There is no Android version of this build step, because the Android SDK already provides this functionality.

Reboot iOS Device

Reboots one or more attached iOS devices. This can optionally be used at the end of a build, to "reset" for the next one.

Note: There is no Android version of this build step, because the Android SDK already provides this functionality ("adb reboot").

Changelog

Version 2.17 (released July 7, 2014)

  • "Play Composition(s)" build step now has support for transaction thresholds.

Version 2.16 (released June 11, 2014)

  • Display full clip path for validation messages (eg. A nested clip will have all clips on its path output, not just its clip name).
  • Blocks cross-site scripting in output of test results.

Version 2.15 (released May 13, 2014)

  • "Play Composition(s)" build step no longer outputs duplicate validation clip names. Clip name formatting has changed to be on individual lines and validation messages belonging to the clip are now indented.

Version 2.14 (released May 5, 2014)

  • Added clip name to "Play Composition(s)" build step's validation output.

Version 2.13 (released April 7, 2014)

  • Dynamic Instrumentation support for "MakeAppTouchTestable" build step.
  • Additional JVM options support for "MakeAppTouchTestable" build step.

NOTE: The "jump" in version numbers from 2.8 to 2.13 is due to technical issues encountered while attempting to release the new version of the plug-in.  There were no releases between 2.8 and 2.13.

Version 2.8 (released February 26, 2014)

  • Null Junit Results are now prevented from triggering bad HTML output in Jenkins.

Version 2.7 (released December 19, 2013)

  • Fixed "403 Forbidden" errors when downloading files using CloudTest plugin.

Version 2.6 (released November 22, 2013)

  • Fixed NullPointerException seen when additional options are not provided for the "Play Composition(s)" build step.

Version 2.5 (released November 08, 2013)

  • Issue where CloudTest servers were not being detected correctly has been resolved.
  • New "Additional Options" input for the "Play Composition(s)" build step.  Any values entered here will be passed directly to SCommand.
  • Server configurations are now managed using a unique ID and friendly name, instead of being bound to the URL.  This means that you can use multiple CloudTest accounts with a single server (e.g. for concurrent builds), and can change the URL for a server configuration without affecting existing jobs.

Version 2.4 (released June 25, 2013)

  • The "Run App in iOS Simulator" build step now works correctly when only a single CloudTest server has been configured.

Version 2.3 (released June 4, 2013)

  • The "Play Composition" build step now works correctly on Windows (JENKINS-17986).
  • Improved error message when the plug-in fails to determine the CloudTest server's build number.

Version 2.2 (released May 14, 2013)

  • The "Run App in iOS Simulator" build step now automatically launches TouchTest Agent on the simulator.
  • Internal changes in preparation for next major CloudTest release.

Version 2.1 (released April 8, 2013)

  • SCommand invocations now "inherit" the Jenkins proxy settings.
  • File and directory validations no longer show an error when the path includes a variable.

Version 2.0 (released March 15, 2013)

  • Initial release.
  • No labels