README.md

Java Demonstration Scripts

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.

🥇Most Popular

• Best practices with multiple testing strategies
• Quick start test, Junit 5
• Quick start test, Junit 4
• Quick start test, TestNg
• iOS real device, native app, Junit4
• Front-end performance testing
• Visual E2E test
• Sauce Connect usage

Best Practices

• Desktop junit4 sauce-bindings
• Emu/Sim Web junit4 sauce-bindings
• Performance junit4 sauce-bindings
• RealDevice junit4 sauce-bindings

🖥Web automation

• Sauce Bindings With TestRunner Examples

  • Junit 5 junit5 sauce-bindings
  • Junit 4 junit4 sauce-bindings
  • TestNg testng sauce-bindings

• Sauce Bindings Examples

  • Junit 5 junit4 sauce-bindings
  • Junit 4 junit4 sauce-bindings
  • TestNg junit4 sauce-bindings

• Selenium Examples

  • Accessibility Test with Sauce Bindings junit4 sauce-bindings
  • Accessibility Test with Deque Axe junit4
  • Cucumber web test
  • Windows authentication junit4
  • Cross Browser/Platform in Parallel w/ TestNG testng
  • Performance, front-end with Sauce Bindings junit5 sauce-bindings
  • Single Browser in Parallel w/ TestNG testng

📱Mobile automation

📚 Mobile Testing Training Tutorials

• Real Devices

  • iOS native app
  • Android native app
  • Upload app to Sauce Storage
  • Image Injection
  • Biometric Login
  • Cucumber w/ Appium junit4 cucumber

• Emulators and Simulators

  • iOS native app
  • Android native app
  • Biometric Login

⚙️Setup

• Install Git

• Install IntelliJ (or another IDE)

• Install JDK

• Install Maven

Import the Project

1. Create a directory on your machine.

2. Clone this repository into the said directory.

   $ git clone https://github.com/saucelabs-training/demo-java.git
   

3. Import the project into IntelliJ (or the IDE of your choice) as a Maven Project.

4. Click through the prompts, and confirm when it asks to Import from Sources

5. Choose the demo-java directory as the root directory of the project.

Set Your Sauce Labs Credentials

1. Copy your Sauce Labs username and accessKey in the User Settings section of the Sauce Labs Dashboard.

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

3. 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%
   

Run a Maven Test

1. Run the following command to update any package dependencies:

   $ mvn dependency:resolve
   

2. Then run the following command to compile your test code:

   $ mvn test-compile
   

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

Contributing

Sauce Labs maintains this repository. We welcome all ideas and contributions!

Guidance for contributing can be found here

Disclaimer

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, and headless, may require a different account tier beyond free trial. Please contact the Sauce Labs Sales Team for support and information.