TestingWhiz


Get Community


  • Solutions
    • Web Test Automation
    • Mobile Testing
    • Cross-Browser Test Automation
    • Regression Test Automation
    • Web Services Testing
    • Data-Driven Testing
    • Database Testing
    • Big Data Testing
  • Features
  • Integrations
  • Pricing
  • Resources
    • Webinars
    • White Papers
    • Infographics
    • Case Studies
    • User Manual
    • Release Notes
    • Download Center
    • User Forum
    • FAQs
  • Blog
  • Company
    • About
    • News & Events
    • Whiz Consulting
    • Partners
    • Contact Us
User Manual
  • General Information
    • About TestingWhiz
    • TestingWhiz Architecture
    • System Requirements
    • Browser and Device Support
  • Understanding TestingWhiz Tool
    • Menu Bar
    • Tool Configuration Settings
    • Third Party Integrations
    • Menu Tab
    • Test Editor Tab
    • Test Commands, Methods and Variables
  • Create and Manage Test Projects
    • Create, Record and Import Test Scripts
    • Create Test Suites
    • Create Test Cases
    • Execute Test Scripts
  • Test Reports
  • Methods Accessing Data Table Values Without Loop
  • Generating Test Data Table
  • Importing Data from Other Test Projects
  • Types of Testing Supported by TestingWhiz
  • Mobile Test Execution
  • Desktop Test Automation
  • Image Comparison
  • Forking & Data Validation
  • Test Execution via CI Plugin
  • Integration with Test Management Tools
  • Integration with Version Control
  • Test Commands & Corresponding Actions
  • Test Commands Reference
    • Web App Commands
    • Mobile App Commands
    • Desktop App Commands
    • Conditional Commands
    • Database Commands
    • Web Service Commands
    • File Operation Commands
    • Script Optimization Commands
    • Desktop Commands

Execution via TestingWhiz CI Plugin

TestingWhiz allows users to execute Test Scripts on the server via TestingWhiz CI plugins such as Jenkins or Bamboo. This lets the user validate her/his application on regression cycles and provide reports to CI tools on a continuous basis

Jenkins:

Steps & Configurations

Here is the process of integrating Jenkins Server with TestingWhiz:

Free Style Project:

1. Download the Jenkins Plugin file from TestingWhiz download page.

2. Place the downloaded plugin file into the .Jenkins home directory

3. Start the Jenkins server and access in the browser

4. Build a Free Style project.

5. Click on Add Build Step and select TestingWhiz Script

Jenkins Configuration

6. Server URL:- Enter the Server address where the TestingWhiz server is running (http://ipaddress:5050/)

7. Base URL[optional]:- Specify Base URL in format (http://host:port/). [Note: Specified value is used only if ‘${BASEURL}’ is given as value in one of the step in .twiz file.]

8. Script Path:- Specify the absolute path of a test case file or users can also specify the folder path where all the test scripts are stored to execute. [Note: Script file should be on a same system where jenkins instance is running and should have all required permissions.]

9. Browser:- Specify the browser for your build by selecting one from the Browser drop-down. Available browsers are Mozilla Firefox, Internet Explorer, Google Chrome, Edge, Headless Execution.

10. Test Object[optional]:- Enter a specific Test suite or Test case to exclusively execute inside the Test Object column or leave it blank to execute the entire script file.

11. Step Execution Interval[optional]:-Specify the interval time between two steps that is to be performed while execution.

12. Report Interval:- Specify the minimum time taken by any case of this script when executed in TestingWhiz tool. Value should be in milliseconds.

Plugin Configuration

13. Tools --> Start Server

14. Test Script is ready to be executed via Jenkins server.

Pipeline Project:

1. Download the Jenkins Plugin file from TestingWhiz download page.

2. Place the downloaded plugin file into the .Jenkins home directory

3. Start the Jenkins server and access in the browser

4. Build a Pipeline project.

5. In Pipeline block, specify below script.

def testingWhiz() {

                        testingWhiz serverUrl: env.TW_SERVER_URL,

                        baseUrl: env.TW_BASE_URL,

                        scriptPath: env.TW_SCRIPT_PATH,

                        browser: env.TW_BROWSER,

                        testObject: env.TW_TEST_OBJECT,

                        stepExecutionInterval : env.TW_STEP_EXECUTION_INTERVAL,

                        reportInterval : env.TW_REPORT_INTERVAL

                        failureScreenshot : false,

                        conditionFailureScreenshot : false

}

properties([

             parameters([

                         string(

                                     name: 'TW_SERVER_URL',

                                     defaultValue: '',

                                     description: 'Dynamic Server URL'

                         ),

                         string(

                                     name: 'TW_BASE_URL',

                                     defaultValue: '',

                                     description: 'Dynamic Base URL'

                         ),

                         string(

                                     name: 'TW_SCRIPT_PATH',

                                     defaultValue: '',

                                     description: 'Dynamic Script Path'

                         ),

                         choice(

                                     name: 'TW_BROWSER',

                                     choices: ['Mozilla Firefox', 'Google Chrome', 'Internet Explorer',                                                                   'Headless Execution', 'Edge'],

                                     description: 'Dynamic Browser'

                         ),

                         string(

                                     name: 'TW_TEST_OBJECT',

                                     defaultValue: '',

                                     description: 'Dynamic Test Object'

                         ),

                         string(

                                     name: 'TW_STEP_EXECUTION_INTERVAL', 

                                     defaultValue: '',

                                     description: 'Dynamic Wait Time'

         ),

                         string(

                                     name: 'TW_REPORT_INTERVAL',

                                     defaultValue: '',

                                     description: 'Dynamic Case Time'

                         )

             ])

])

node{

                        stage('TestingWhiz'){

             testingWhiz()

                        }

}

Pipeline Configuration

[Note: TW_SCRIPT_PATH:- Script file should be on a same system where jenkins instance is running and should have all required permissions. TW_BASE_URL:- During script file creation ‘${BASEURL}’ needs to be provided as value in one of the step.]

6. Tools --> Start Server.

7. Save the configuration and then execute using ‘Build with Parameters’.

8. Specify the mandatory field values and then click ‘Build’.

[Note: To avail Jenkins integration functionality on your TestingWhiz, email at sales@testing-whiz.com]

Refer YouTube Link - Test Script Execution over Jenkins

Bamboo:

Steps & Configurations

1. Download the TestingWhiz Bamboo Plugin file from TestingWhiz download page

2. Place the downloaded plugin file into the bamboo-home directory under system user directory

3. Start the Bamboo server and access in the browser

4. Build one bamboo plan with one task created using TestingWhiz script plugin option

Bamboo Configuration

Bamboo Plugin Configuration

6. Enter the Server address where the TestingWhiz server is running (http://ipaddress:5050)

TestingWhiz Bamboo Configuration

7. Specify the absolute path of a test case file or users can also specify the folder path where all the test scripts are stored to execute.

8. Specify the browser for your build by selecting one from the Browser drop-down

9. Enter a specific Test suite or Test case to exclusively execute inside the Test Object column or leave it blank to execute the entire script file (optional).

10. Specify the interval time between two steps that is to be performed while execution (optional)

11. Go to Tools → Start Server

12. Test Script is ready to be executed via Bamboo Server

Bamboo Server

Refer YouTube Link - Test Script Execution over Bamboo

Azure DevOps:

Steps & Configurations

• Risk-Based Testing: Select this option to achieve Risk Based Testing in Azure DevOps using TestingWhiz plugin.

• Test Object Execution: Select this option to select a specific Test Suite/Test Case from the script to execute.

In This Section
  • Jenkins
  • Bamboo
  • Azure DevOps
PREVIOUS
NEXT
cygnetinfotech

About

TestingWhiz is committed to provide an innovative and automated software testing solution to the global enterprises and software companies for their web, mobile and cloud applications.

location

Cygnet Infotech LLC,
125 Village Boulevard,
Suite 315, Princeton,
NJ 08540, USA

PHONE | EMAIL

1-855-699-6600
info@testing-whiz.com

Get Started

Download Trial
Demo
Pricing
Contact Us
  • Privacy Policy
  • Terms of Use
 
TestingWhiz Capterra Ratings

Copyright© 2021, TestingWhiz. All Rights Reserved.

This website uses Cookies to improve site’s functionality & provide you with better browsing experience. Detailed information on the use of cookies on this website, and how you can decline them, is provided in our Cookie Policy. If you don't agree, kindly disable cookies from browser settings.