Jenkins
Space shortcuts
Child pages
  • CrossBrowserTesting Plugin

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
  • Created by Unknown User (crossbrowsertesting), last modified on Sep 21, 2016
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 9 Next »

CrossBrowserTesting.com Jenkins Plugin

This plugin integrates Jenkins users with Selenium Testing and Screenshot Testing on CrossBrowserTesting.com. CrossBrowserTesting.com provides cross browser testing of websites, webpages, and web applications on Windows, Macs, and real iPhones, iPads, and Android Phones and Tablets.

Features

  1. Running Selenium Scripts in Python, Ruby, Java, CSharp, and Javascript on CrossBrowserTesting.com
  2. Running Automated Screenshot Testing on CrossBrowserTesting.com
  3. Automated Starting and Stopping of the CrossBrowserTesting.com NodeJS local tunnel to test local and development webpages behind your firewall

Installation

via the interface
  1. Go to your installation's management screen.
  2. Click Manage Plugins.
  3. Click the Available tab.
  4. Find the CrossBrowserTesting.com Plugin and select the checkbox.
  5. then click either Install without restart or Download now and install after restart.
by hand(not recommended)
  1. Download CrossBrowserTesting.hpi.
  2. Save the downloaded .hpi file into your `$JENKINS_HOME/plugins` directory.
  3. Restart Jenkins.

Configuration

Environment Variables

The CrossBrowserTesting.com Jenkins Plugin passes your build step information to your Selenium scripts as environment variables. The exact syntax will vary depending on your scripting language.

Variable

Description

CBT_USERNAME

the username used on CrossBrowserTesting.com for Selenium Testing

CBT_APIKEY

the apikey used on CrossBrowserTesting.com for Selenium Testing

CBT_BUILD_NAME

the Jenkins Project's name

CBT_BUILD_NUMBER

the Jenkins Project's current build number

CBT_OPERATING_SYSTEM

the apiname of the selected Operating System

CBT_BROWSER

the apiname of the selected Browser

CBT_RESOLUTION

the name of the selected Screen Resolution

See the examples directory for a few language specific sample scripts.

Saving Your CrossBrowserTesting.com API Credentials
  1. Go to your installation's management screen.
  2. Click Configure System.
  3. Find the section labeled CrossBrowserTesting.com.
  4. Enter your CrossBrowserTesting.com Username and API Key information. You can find your api key here (must be logged in)
  5. Click Save.
Build/Configure
Version >= 0.11 Build Environment
  1. Configure your Jenkins Project.
  2. In Build Environment, Check the box next to CrossBrowserTesting.com
  3. For Screenshot Tests: Pick a BrowserList and enter a URL (you must have you API credentials saved for the browserlist to populate)
  4. For Selenium Tests: Add the Operating System, Browser, and Screen Resolution that you want to run a Selenium Test on. You can add multiple configurations by clicking Add Selenium Tests
  5. Click Save
  6. Click Build Now to build the project. All files in the project's workspace will be ran (make sure the selenium scripts are executable). Output from the selenium script will be displayed in Console Output for the build.
  7. Optional: Check Use Local Tunnel to run tests on webpages behind your firewall. (The CBT NodeJS Tunnel must be installed globally.)
Version <= 0.10 Build Step
  1. Configure your Jenkins Project.
  2. Click Add build step.
  3. Click CrossBrowserTesting.com.
  4. Add the Operating System, Browser, and Screen Resolution that you want to run a Selenium Test on. You can add multiple build steps to run multiple selenium tests.
  5. Click Save
  6. Click Build Now to build the project. All files in the project's workspace will be ran (make sure the selenium scripts are executable). Output from the selenium script will be displayed in Console Output for the build.
  • No labels