Project : Provar Project with Bitbucket

 Configuring Your Provar Project

To set up Bitbucket Pipelines, you must first create and configure the bitbucket-pipelines.yml file in the root directory of your repository.

You also need to configure the Provar project and the other required files to publish it on the Bitbucket repository.

  • ProvarProject: It contains the files built in Provar, such as test cases, the src folder, build.xml files, etc.
  • Provar License: This includes the .license folder containing execution licenses.

Build.xml Configuration

Edit the below information in the build.xml file.

  • provar.home: This value is the path of the ProvarHome folder, which contains the latest ANT libraries
  • testproject.home: This value is the Provar project root in your repository
  • testproject.results: The Provar results directory in your repository
  • license.path: This is the path where the .license folder is located
<project default="runtests">
<property environment="env"/>
<property name="provar.home" value="${env.PROVAR_HOME}"/>
<property name="testproject.home" value=".."/>
<property name="testproject.results" value="../ANT/Results"/>
<property name="secrets.password" value="${env.PROVARSECRETSPASSWORD}"/>
<property name="testenvironment.secretspassword" value="${env.ProvarSecretsPassword_EnvName}"/>
<taskdef name="Provar-Compile" classname="com.provar.testrunner.ant.CompileTask" classpath="${provar.home}/ant/ant-provar.jar"/>
<taskdef name="Run-Test-Case" classname="com.provar.testrunner.ant.RunnerTask" classpath="${provar.home}/ant/ant-provar.jar;${provar.home}/ant/ant-provar-bundled.jar;${provar.home}/ant/ant-provar-sf.jar"/>
<taskdef name="Test-Cycle-Report" classname="com.provar.testrunner.ant.TestCycleReportTask" classpath="${provar.home}/ant/ant-provar.jar;${provar.home}/ant/ant-provar-bundled.jar;${provar.home}/ant/ant-provar-sf.jar"/>
<target name="runtests">
<Provar-Compile provarHome="${provar.home}" projectPath="${testproject.home}"/>
<Run-Test-Case provarHome="${provar.home}"
projectPath="${testproject.home}"
resultsPath="${testproject.results}"
resultsPathDisposition="Increment"
testEnvironment=""
webBrowser="Chrome_Headless"
webBrowserConfiguration="Full Screen"
webBrowserProviderName="Desktop"
webBrowserDeviceName="Full Screen"
excludeCallableTestCases="true"
salesforceMetadataCache="Reuse"
projectCachePath="../../.provarCaches"
testOutputlevel="WARNING"
pluginOutputlevel="WARNING"
stopTestRunOnError="false"
secretsPassword="${secrets.password}"
testEnvironmentSecretsPassword="${testenvironment.secretspassword}"
invokeTestRunMonitor="true"
>
<fileset id="testcases" dir="../tests"></fileset>
</Run-Test-Case>
</target>
</project>

Creating a Project in Bitbucket

Step 1: Log in to your Bitbucket account.

Step 2: Create a new repository and list the project name, repository name, and visibility level.

Creating a Project in Bitbucket

Step 3: Push the project configured above to the repository.

Configure your Bitbucket Pipelines

Step 1: Go to Pipelines.

Step 2: Change the template to Other. Now we need to configure the bitbucket-pipelines.yml file.

Image showing how to access Pipelines to start the configuration

Image showing how to change the template to configure the pipelines

Image showing the bitbucket-pipelines.yml file configuration script

Here is an example:

image: atlassian/default-image:2
pipelines:
default:
- step:
services:
- docker
script:
- apt-get update && apt install wget unzip xvfb
- wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add -
- echo 'deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main' | tee /etc/apt/sources.list.d/google-chrome.list
- apt-get update
- apt-get install google-chrome-stable -y
- export PROVAR_HOME="$BITBUCKET_CLONE_DIR/ProvarHome"
- mkdir $BITBUCKET_CLONE_DIR/ProvarHome
- curl -O https://download.provartesting.com/latest/Provar_ANT_latest.zip
- unzip -o Provar_ANT_latest.zip -d ProvarHome
- rm Provar_ANT_latest.zip
- cd ${BITBUCKET_CLONE_DIR}/test/ANT
- xvfb-run ant -f build.xml
artifacts: # defining the artifacts to be passed to each future step.
- test/ANT/Results/*

Explanation of the Sample Script Above

First, we must mention the base docker image – Provar supports Java version 8, and test case execution requires ANT. So, we have taken the official photo of atlassian/default-image:2. We can also use frekele/ant:1.10.3-jdk8 image, which already has Java 8 and ant.

PROVAR_HOME is the folder’s path containing the latest Provar ANT files. This is referenced in the build.xml provar.home property.

We need to execute our UI test cases on a browser which is why the Chrome installation is included. To execute test cases in headless mode, we also need to install xvfb. Before executing the test script section, install xvfb and run the xvfb service. Execute your test cases using the xvfb-run ant -f build.xml command.

Reports and Artifacts

Step 1: To get the reports folder as artifacts in Bitbucket Pipelines, add the following in bitbucket-pipelines.yml.

artifacts: # defining the artifacts to be passed to each future step.
- test/ANT/Results/*

Step 2: Now, commit the file. This will create a file named bitbucket-pipelines.yml in your Bitbucket repository.

Image showing the bitbucket-pipelines.yml file created in the Bitbucket repository

Step 3: Go to Pipelines. You can see your pipeline running.

Image showing the Bitbucket Pipelines running

Step 4: Click on the Artifacts Tabs. You can download the artifacts here.

Image showing the Artifacts Tab

Parameterization using Environment Variables

Parameterizations can be used to execute the following:

  • Using the secrets and environments password
  • Adding data to the build.xml file at run time

To add variables to the repository, follow the below steps:

Step 1: Click the Repository Settings.

Step 2: Add a variable for the secret password. Mark it as secure, which will mask the value.

Step 3: Add a variable for the browser as well. This will help you to define the browser where the execution will be performed.

Parameterization using Environment Variables

You can access the variables using the ${env.VARIABLENAME} format in the build.xml file, as shown in the screenshot below.

Image showing how to access the environment variables in the build.xml file

Parallel Testing

You can achieve parallel testing by configuring parallel steps in Bitbucket Pipelines. Add a set of steps in your bitbucket-pipelines.yml file in the parallel block. These steps will be initiated in parallel by Bitbucket Pipelines so they can run independently and complete faster.

Here is an example:

image: "frekele/ant:1.10.3-jdk8"
pipelines:
default:
- step:
name: No parallel tag
services:
- docker
script:
- echo "Without parallel Tag"
- parallel:
- step:
name: Parallel 1
services:
- docker
script:
- apt-get update && apt install wget unzip xvfb
- wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add -
- echo 'deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main' | tee /etc/apt/sources.list.d/google-chrome.list
- apt-get update
- apt-get install google-chrome-stable -y
- cd test/ANT && xvfb-run ant -f build.xml
artifacts: # defining the artifacts to be passed to each future step.
- test/ANT/Results/*
- step:
name: Parallel 2
services:
- docker
script:
- apt-get update && apt install wget unzip xvfb
- wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add -
- echo 'deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main' | tee /etc/apt/sources.list.d/google-chrome.list
- apt-get update
- apt-get install google-chrome-stable -y
- cd test/ANT && xvfb-run ant -f build.xml
artifacts: # defining the artifacts to be passed to each future step.
- test/ANT/Results/*

Job Scheduling

You can schedule your jobs in Bitbucket Pipelines. 

Step 1: Go to Pipelines.

Step 2: Click on Schedules.

Step 3: Select your branch, pipeline, and schedule (i.e., Hourly, Weekly, or Daily). This will schedule your run as per the configuration.

Image showing how to schedule jobs in Bitbucket Pipelines

Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources...
Read more

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed withou...
Read more