Welcome to Java Demo Scripts, a set of examples showing how to use Sauce Labs technologies. This repository contains everything you need to start with web, mobile, functional, and all other types of Java automation.
junit4
sauce-bindings
junit4
sauce-bindings
junit4
sauce-bindings
junit4
sauce-bindings
Sauce Bindings With TestRunner Examples
Sauce Bindings Examples
Selenium Examples
junit4
sauce-bindings
junit4
junit4
testng
junit5
sauce-bindings
testng
📚 Mobile Testing Training Tutorials
Real Devices
Emulators and Simulators
Install Git
Install IntelliJ (or another IDE)
Install JDK
Install Maven
Create a directory on your machine.
Clone this repository into the said directory.
$ git clone https://github.com/saucelabs-training/demo-java.git
Import the project into IntelliJ (or the IDE of your choice) as a Maven Project.
Click through the prompts, and confirm when it asks to Import from Sources
Choose the demo-java directory as the root directory of the project.
Copy your Sauce Labs username and accessKey in the User Settings section of the Sauce Labs Dashboard.
Open a Terminal window (command prompt for Windows) and set your Sauce Labs Environment
variables:
Mac OSX:
$ export SAUCE_USERNAME="your username"
$ export SAUCE_ACCESS_KEY="your accessKey"
Windows:
> set SAUCE_USERNAME="username"
> set SAUCE_ACCESS_KEY="accessKey"
To set an environment variable permanently in Windows, you must append it to the
PATH
variable.Go to Control Panel > System > Windows version > Advanced System Settings > Environment Variables > System Variables > Edit > New
Then set the "Name" and "Value" for each variable
Test the environment variables
Mac OSX:
$ echo $SAUCE_USERNAME
$ echo $SAUCE_ACCESS_KEY
WARNING FOR UNIX USERS!
If you have problems setting your environment variables, run the following commands in your terminal:
$ launchctl setenv SAUCE_USERNAME $SAUCE_USERNAME
$ launchctl setenv SAUCE_ACCESS_KEY $SAUCE_ACCESS_KEY
Windows:
> echo %SAUCE_USERNAME%
> echo %SAUCE_ACCESS_KEY%
$ mvn dependency:resolve
$ mvn test-compile
Finally, run the following test to see if you've properly configured the test environment:
$ mvn test -pl best-practice -Dtest=DesktopTests
You can run different tests from different modules. Check out some examples by looking at the CI YML files
Sauce Labs maintains this repository. We welcome all ideas and contributions!
Guidance for contributing can be found here
The code in these scripts is provided on an "AS-IS" basis without warranty of any kind, either express or implied, including without limitation any implied warranties of condition, uninterrupted use, merchantability, fitness for a particular purpose, or non-infringement. These scripts are provided for educational and demonstration purposes only and should not be used in production. Issues regarding these scripts should be submitted through GitHub. These scripts are maintained by the Technical Services team at Sauce Labs.
Some examples in this repository, such as
appium-example
,parallel-testing
, andheadless
, may require a different account tier beyond free trial. Please contact the Sauce Labs Sales Team for support and information.